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 2d3124c67f 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 4585e28636 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 75354a9687 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards ffe87e134c 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 7026c4a4ff 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards e09132aa5a 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 620156eefd 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards b78148a4b4 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 09521053bb 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 6d1e9237b9 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards ae730f9a63 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 3a36c4dc64 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 59f3fe9877 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards b489a8765f 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards b37df7a463 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards a79083f48e 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 3489812cbb 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 173b284e1f 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 5ab17e2813 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 6bc78d5a95 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards acd04c7cc6 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards f353f22a52 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards cc530debb4 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 010d8dc0ed 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 8120f24d93 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 4f78c756f2 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 876bf63c6c 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 1f66384791 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards caca714cdb 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 1a16154c79 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 02158caf91 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 363a466122 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 31e75f59ca 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 349249c466 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 05a6484673 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 34fd7ca8b8 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards a37f8ee14a 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 3a451a5701 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards b1be50e738 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 3c776889ca 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 06ca04e40c 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 5f1aac4c2a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 9aae9398d5 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 22361ed8dd 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 95f6d6bce2 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 5c5aecc9d1 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 0df4b89bce 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards da7ff768f4 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 972674cb5a 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 382beb55a1 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 152ea074dc 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 4efef1193e 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 0d5d6eca9e 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 80fa3b3fcd 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards d9c1c2e89c 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 87c520c218 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 924539339c 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 39e3c5c546 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 02ab516e3c 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards a8fad08101 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 1ae626b64b 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 4cf933f2e4 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards c309022ac4 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 61d4657069 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 050a2e668f 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 73ed7331a6 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 164e7f8f96 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards eafa2e06bc 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 9d1fe3ab36 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards f3ddcd4bb5 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 2a976e9f54 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 7a33c1bf14 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards ef4ee63824 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 2cdf15a8a7 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards d95cf3c9bb 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 71917f590f 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards cbd98dfd5d 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards c9fb7e771c 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 3cad8f9c2b 295: onsuccess: #2545: 1: Success after linux: 10 commits discards ed3cdc6ed0 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 4fda78eefc 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 16068e1d47 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards a70c81ddbc 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 577d76dae5 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 7282d12706 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 4c6972cbe3 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 76094619d5 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 238de3a864 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 2108651ea7 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 665aae6e31 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards aa11747f65 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards e3c32c2d19 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards a5e707d74a 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 7486cd48b3 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 3a3251d240 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards dc98f0f86c 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 2b234ef6ce 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards a81f1548bc 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards ecef809f00 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards aac174a962 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 3e9e64a2b4 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 7b43f96676 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 33e1ed82b8 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new c0d829a0c4 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new e348a5cb9b 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 365809a241 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new a1d0c8f410 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new da490ce189 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new f92ebc816a 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 731b9313fd 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new f145225c7c 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new cb6e2d3b70 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 356456ec36 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new db93ab1a94 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 44f02960dd 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 316d60461a 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 8f1e74ebd2 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 8b538ae260 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 3d5a0fec63 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new df3bc089ca 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 9cb428ef05 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 574d1b6097 293: onsuccess: #2542: 1: Success after gcc: 5 commits new aca26e2660 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new a294aeff3e 295: onsuccess: #2545: 1: Success after linux: 10 commits new 83d3738671 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 8a73ecedc9 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 34c10857fa 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 94c42e5054 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 8ba993f604 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new ecf87f3afc 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 034cad5d4f 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new c249ebafd7 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 5dbe901c3f 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new b2584bbe2d 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 9464d49da3 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new a94b869d8b 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 6236dfb465 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new b59bb46299 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 9bced152c1 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new f5e3e6918d 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 3c74c56551 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 20c7ac0336 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 6f0e850205 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 1882f21f46 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new e0d909a251 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 3c398abb4d 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new f0648d96d1 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 6e96c5f798 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 296e4e7cab 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new fc55b8db04 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new fd5970276a 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 3828896ec1 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 663865296d 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new a48ffd5ffa 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 3b8b7e5a70 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 2749607c17 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 617be8d4cc 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 1fc838ff95 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 9139b685e5 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 4f67342566 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new ce89d7a27e 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 2cd67fb261 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new ced03ff053 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new bc851f7dad 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new e20d69e3af 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new c867eded4f 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 062533bb65 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 15ebdd0a14 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 3ef530ad4f 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new c31f181039 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 84de6b2515 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new ca9cd45413 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 815b4c9e8c 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new fe2f804d7a 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 53c4a3bd70 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new e41642b999 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 4c0ed51e7c 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new bd377bed1e 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 484ca29312 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 4db8afdf49 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 1c84d2bd9c 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 1614695ae5 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new cee74fe1a4 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 2d69bfb7cb 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 0ef21c92c9 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new e2e324a942 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 3bbec08a1c 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 9450b1d3e7 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new dd3438f6b4 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 42bcbe6aa9 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new f9b68eb3b2 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 142f0fef9a 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 0f10f918d0 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 12cf4f6e42 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 575d925fc9 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new fd9a1c8ed7 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 0a1e8ef8c5 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 5e2d89c408 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 88ef860e2d 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 4566dadbf4 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 4144a1adba 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new accd5bb0f9 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new bfc43eb429 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits

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 (2d3124c67f) \ 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 1824 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 32876 -> 31900 bytes 04-build_abe-stage1/console.log.xz | Bin 74076 -> 74300 bytes 06-build_abe-linux/console.log.xz | Bin 8648 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 247608 -> 246704 bytes 08-build_abe-stage2/console.log.xz | Bin 207980 -> 208692 bytes 09-build_abe-gdb/console.log.xz | Bin 40304 -> 38964 bytes 10-build_abe-qemu/console.log.xz | Bin 33040 -> 32800 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3364 -> 2712 bytes 13-check_regression/console.log.xz | Bin 8244 -> 7104 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 24 +- 13-check_regression/mail-body.txt | 104 +- 13-check_regression/results.compare | 58 +- 13-check_regression/results.compare2 | 189 +- 13-check_regression/results.regressions | 58 +- 14-update_baseline/console.log | 66 +- 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 | 106 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 58 +- sumfiles/g++.log.xz | Bin 3401740 -> 3390656 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 3032424 -> 3022468 bytes sumfiles/gcc.sum | 4345 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1044288 -> 1032500 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 215324 -> 215052 bytes sumfiles/libgomp.sum | 12 +- sumfiles/libitm.log.xz | Bin 2660 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438344 -> 436824 bytes sumfiles/libstdc++.sum | 337 ++- 42 files changed, 2802 insertions(+), 2649 deletions(-)