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 d68dc19bd7 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards f21bc893be 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards ac3fcd0404 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 9e938ccc4e 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards ef620fccba 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 69b477696f 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 6843dd183b 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards bf5990d0c5 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 2aa09b0972 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 534ab815fd 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 0a9c84fc03 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 003fbd17f0 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 803584f3e8 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 115cbd12e1 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards fbd11072fe 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 583919ce28 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 52c1cbaa2e 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards fb5f7b4bd2 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 69eaadc640 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 29737a1e43 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 1b9f564442 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards ed68104fad 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 24f8135070 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 0806f20ba5 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards e8bb77800c 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards c5a3294a80 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards c4e91fb671 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 59cc1ded36 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards ced9286ea0 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 58f71b9de2 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards a09c8bdb65 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards fdbdd0b536 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 3152af3084 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards b47df5c03e 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards b4e2ba4415 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 77b7843b61 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards ec52a097ac 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards be9addda37 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 7a573c0ee6 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 334ed6eb5a 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 9f299baeb8 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 98c5a88af9 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 248466476f 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 6ea6e6aa8c 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards c90a7c2d84 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 536ca47129 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards d8e510ade7 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 38ab015bb3 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 49f09fc909 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 082b372837 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards a0583c5177 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 99e395db58 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 734617a864 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards d1faabcd42 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 58694895cc 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 5717db8861 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 67a86f04c3 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 6c3efe436d 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 3641200c7e 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 6dcc2ce109 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 83c244a4fa 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards a770d21d76 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 9e62fc3828 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 7c78e75f61 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards ea35de1b05 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards e57e1aeda6 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 924de64962 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 3ec23de5be 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 0ff5fad00e 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 6799b177b1 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 3343bd2873 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards d22b9b3453 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 511bd2b030 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards c4cb52fff0 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 7b4bfa2e91 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 678acae34b 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards b4b21a7b4b 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 202c2bad31 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 633b45fb13 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 707897c200 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 8cf0ca3739 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 7f600b2c61 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 1ce1d9c328 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 9b54cb8321 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 685595942f 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 826c9e7ffe 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 09bb08c0a6 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 274521c660 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 8947d48da4 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 21da3819cc 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 832936d840 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 1eefec6731 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 1b09520e3f 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 2d42c929c9 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 3f67555bdc 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 20267350a2 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 867739fc86 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 2df411616d 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards eb24289a7a 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 2e816550a3 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards df5bbd0c32 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new a16e533ad0 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 9c2d56a401 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new ea986adf07 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new dcd9e74281 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new cae96cd355 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 6ca86c7cad 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 83bd659018 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new c77d071521 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 1f5c2e76c0 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 8227780773 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 84f36d2e01 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 781a77fdfe 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 2b90d89c2b 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 96bd706d33 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new ae933fe342 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 2ab0ce250c 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 3afb7f3177 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 235de4503e 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 4793b2524e 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new c9fd8e0431 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new af87ff26bb 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 997fdcd215 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new cae6a3cdea 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 4685c0c14e 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 35f8b62983 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new e2cbd3dab7 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new be5b4ed5ed 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new f66bc439c9 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 62921269ac 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 56143cd37b 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 6f842632c4 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new eacd877852 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 23b4ec4070 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 663dbe3573 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 7e53de1a1f 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new bb8ccc6d71 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 5f773b743d 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 09988b3806 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 01621fd62c 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 094b40e29e 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 4460bab87e 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new e99895eea1 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new fa15838517 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 47e79e230c 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new e1525f3f8b 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new d9801d0c89 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 422be20b4a 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 4898188df4 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 219c7ab076 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 1ad9fd514f 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 19f574b2c6 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 09463f2312 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 5575dd85b0 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 0e2d56cd3d 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 1c4b50ad0e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new a445ae940e 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 5deb1c26dd 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new c0883c1644 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new ea89d76664 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new ffd349c942 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 718b537084 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 8dc1642027 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new c002424db8 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new f1a3b2c14f 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 887968b25f 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 9f7d10018c 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 9b934473d0 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new d8c8e0d8f4 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new dd8fda801e 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 16cafad5dd 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new a0d35f5da3 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 84c5c2f6a0 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 85fcb2c899 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new d0efd66b27 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new cdec0198a4 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new dc62902c2b 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 153e417c5c 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 812faf6394 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 03606598c8 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 89b9a74751 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 1f00ed0dff 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 18830ce726 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 8abdb27eb4 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 3c22b59917 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new b85cc4d25a 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 14260fb159 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 1f995c9096 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new c353d97ccc 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new a41552b5de 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new f16ec07114 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new f2432365dd 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new ad4ec7cacc 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 70d3d2a455 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 8db7781d4c 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new a5a876fdad 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 6ea459fd9c 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 6b3eee4581 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 507c776293 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new f246fb6202 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 991b37a294 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 589dc4e867 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 30720ace6c 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...]

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 (d68dc19bd7) \ 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 1764 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31188 -> 31360 bytes 04-build_abe-stage1/console.log.xz | Bin 73408 -> 73316 bytes 06-build_abe-linux/console.log.xz | Bin 8544 -> 8608 bytes 07-build_abe-glibc/console.log.xz | Bin 244288 -> 245008 bytes 08-build_abe-stage2/console.log.xz | Bin 204504 -> 204972 bytes 09-build_abe-gdb/console.log.xz | Bin 38308 -> 38656 bytes 10-build_abe-qemu/console.log.xz | Bin 32452 -> 32608 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3936 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3056 -> 2640 bytes 13-check_regression/console.log.xz | Bin 7120 -> 6288 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 71 +- 13-check_regression/results.compare | 36 +- 13-check_regression/results.compare2 | 74 +- 13-check_regression/results.regressions | 36 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 73 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 36 +- sumfiles/g++.log.xz | Bin 3412204 -> 3382096 bytes sumfiles/g++.sum | 47 +- sumfiles/gcc.log.xz | Bin 3025540 -> 3023256 bytes sumfiles/gcc.sum | 4384 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1039408 -> 1038624 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217664 -> 217592 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437948 -> 436124 bytes sumfiles/libstdc++.sum | 66 +- 41 files changed, 2484 insertions(+), 2464 deletions(-)