This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 71570ba29b 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 864c453eb5 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 7893cdf4b7 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 2457513420 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards c1c25e93d6 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 93da227ede 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards c2fa6e7503 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 0db0116bdd 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 522944fab2 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 6de7419b25 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards afca38bb73 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards f2ad1184d3 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 3366e957ff 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards b4b74882ed 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards f1eb4f49b3 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 0cd7c22ceb 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 9b6357ffe2 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 4769cb1b9c 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 02f122b857 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards c868121306 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 5b5939a606 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 2acaf56276 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards db8c1afb9e 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards eb97bf4f74 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 041b62f78d 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 15e43914d1 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 3eca9a0e79 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 668812d83a 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 61b74cc626 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards d36199acf3 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 362b3138ff 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards df87b83706 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards fc0a4090b7 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 24f1aa4f64 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 6e4762c9ba 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 65b1f462b5 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 72770b5ae4 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 3f6bc4fa23 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards abd5bfbbf1 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 0c2bb2f0f8 295: onsuccess: #2545: 1: Success after linux: 10 commits discards ea96beb269 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 75a22d01bc 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 7a0e71d715 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 1e864649b7 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 7f49ec4d4e 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 3e95859e21 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 1bcaa99f09 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards a1d78e2b39 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 8ab902a6f7 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards e77322a5c3 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 561e199851 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 8cda172fcc 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards e7d0ab03e5 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards dba22d2d77 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 09290f71f9 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 87887cbb91 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 31eb0d09e5 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards ade07522b9 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 456e252e13 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 7a37f808a2 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 24799fa338 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards f3ec40af19 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 46f115f92b 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 950aef12f2 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 49c2f87f25 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards e7cf46ca55 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards d5a09d9e01 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards d823965d88 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 68122f1c9a 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 694e2fb0aa 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 1708146dfd 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards da29bb6a87 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 56f7c0bc03 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 5f3f15794c 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards e3c5f8a563 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards e5c7d5ee61 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards a5f37b8389 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 7a46624e09 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards bc5c8b4de8 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 125bd104dd 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards ef120c904a 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 01f01e65ae 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 191cad374f 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards a23935c6b6 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 6f180dd6e0 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 98b302510a 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards f21ac6bda4 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards ec5e2a5021 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 780644081b 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards f199257bcb 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 8682e93d11 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 1c293e6fd2 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 85988a93cf 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards a1235dbe03 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards b4ebf905d7 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards a1ab5c0e11 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 77b77cae32 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 775f3fc246 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 007ae9dac8 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 2ab8cf471c 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 3ec79e5d52 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 1e9c440590 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new a9310d5616 235: onsuccess: #2483: 1: Success after linux: 108 commits new a46977e1a6 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 31b930eb26 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new dfb3da9d78 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 2a67a3cdf9 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 7c00d5073e 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 2f25d0e42e 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 71562a6675 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 8a84aab4b7 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new fff8ea1c50 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 1161910e86 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 6fb804b3bc 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new e7a8e839f6 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new f0f98a1b7b 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new b2158de6a9 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 169dbcd9e6 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 3162cdfdf9 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new f0a6f3c8f0 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 65088749d8 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 07e926185f 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 82d902a69d 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 3a772c204e 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new d89e6b49bf 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 626f74f707 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 5451afcc1a 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new a2d500dce7 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 058403c5d5 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new e3e3bb752e 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 5a076ee39b 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 2da347d9b7 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new e55a4d0be9 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new bc9311b66d 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 9fc61b9d40 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 1683c14e2d 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 1d1c6359f7 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new e201969b27 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 47a31edee6 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 0142366265 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 8aab58bb22 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 6e464a9525 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 644b9022bc 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 543ffe80a2 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new d2677f0e64 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new f3d280ca9c 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new bec4bce3bf 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 108cd13b9e 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 6891349b1b 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new ac7e24b346 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 390fe2cec3 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new a3d7f51e26 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 41a891a54e 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 6b13c9f458 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 1b04675e55 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 039346369a 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 82a8e0a64c 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 0cd708874c 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new a58a4094fc 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 125181905e 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 35f1b0c597 293: onsuccess: #2542: 1: Success after gcc: 5 commits new eb8162eb7e 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 44fef0ef89 295: onsuccess: #2545: 1: Success after linux: 10 commits new 754a44bc99 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new fb2cc6a0d3 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new b43db2fc96 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 225a9d8363 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 6bb31fdf2d 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 23d4f2a10a 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new f05096f025 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 326b3ea465 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 1eac558742 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 48c42db822 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new d80b9ada84 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new b27cfb5341 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 6117a823e7 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new fdcd9c00d6 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new c45339fb2c 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new bd3efce23e 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 51682b51f4 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 649209d942 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 8c42d55aa0 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 182129cdbc 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new a47aa7ca09 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 9b8b60dfb4 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new d0c2c6a342 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new fd9bdb286c 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new a5bebaa560 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 668219f036 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 96cfb155fe 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 97a39f2c05 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 9b53cc942d 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 45212405f8 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 1fca2fdd53 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new f3b1499a9e 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 6490049071 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new fc9f8aacd8 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new f3961102da 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 5698af0224 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new ecea0af00f 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 167f596543 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new ff494a9555 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 1a6dcb8832 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...]
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (71570ba29b) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31752 -> 31968 bytes 04-build_abe-stage1/console.log.xz | Bin 73200 -> 73368 bytes 06-build_abe-linux/console.log.xz | Bin 8668 -> 8736 bytes 07-build_abe-glibc/console.log.xz | Bin 245120 -> 245656 bytes 08-build_abe-stage2/console.log.xz | Bin 204328 -> 204648 bytes 09-build_abe-gdb/console.log.xz | Bin 39120 -> 39300 bytes 10-build_abe-qemu/console.log.xz | Bin 32380 -> 32484 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3932 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2780 -> 2812 bytes 13-check_regression/console.log.xz | Bin 6904 -> 7132 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 37 +- 13-check_regression/mail-body.txt | 135 +- 13-check_regression/results.compare | 62 +- 13-check_regression/results.compare2 | 135 +- 13-check_regression/results.regressions | 62 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 137 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 62 +- sumfiles/g++.log.xz | Bin 3408304 -> 3402424 bytes sumfiles/g++.sum | 49 +- sumfiles/gcc.log.xz | Bin 3043468 -> 3040476 bytes sumfiles/gcc.sum | 4001 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1037268 -> 1037496 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214852 -> 214572 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430296 -> 432144 bytes sumfiles/libstdc++.sum | 18 +- 43 files changed, 2327 insertions(+), 2499 deletions(-)