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 1a6dcb8832 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards ff494a9555 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 167f596543 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards ecea0af00f 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 5698af0224 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards f3961102da 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards fc9f8aacd8 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 6490049071 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards f3b1499a9e 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 1fca2fdd53 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 45212405f8 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 9b53cc942d 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 97a39f2c05 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 96cfb155fe 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 668219f036 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards a5bebaa560 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards fd9bdb286c 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards d0c2c6a342 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 9b8b60dfb4 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards a47aa7ca09 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 182129cdbc 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 8c42d55aa0 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 649209d942 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 51682b51f4 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards bd3efce23e 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards c45339fb2c 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards fdcd9c00d6 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 6117a823e7 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards b27cfb5341 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards d80b9ada84 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 48c42db822 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 1eac558742 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 326b3ea465 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards f05096f025 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 23d4f2a10a 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 6bb31fdf2d 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 225a9d8363 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards b43db2fc96 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards fb2cc6a0d3 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 754a44bc99 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 44fef0ef89 295: onsuccess: #2545: 1: Success after linux: 10 commits discards eb8162eb7e 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 35f1b0c597 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 125181905e 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards a58a4094fc 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 0cd708874c 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 82a8e0a64c 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 039346369a 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 1b04675e55 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 6b13c9f458 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 41a891a54e 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards a3d7f51e26 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 390fe2cec3 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards ac7e24b346 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 6891349b1b 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 108cd13b9e 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards bec4bce3bf 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards f3d280ca9c 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards d2677f0e64 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 543ffe80a2 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 644b9022bc 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 6e464a9525 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 8aab58bb22 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 0142366265 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 47a31edee6 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards e201969b27 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 1d1c6359f7 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 1683c14e2d 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 9fc61b9d40 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards bc9311b66d 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards e55a4d0be9 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 2da347d9b7 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 5a076ee39b 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards e3e3bb752e 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 058403c5d5 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards a2d500dce7 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 5451afcc1a 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 626f74f707 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards d89e6b49bf 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 3a772c204e 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 82d902a69d 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 07e926185f 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 65088749d8 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards f0a6f3c8f0 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 3162cdfdf9 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 169dbcd9e6 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards b2158de6a9 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards f0f98a1b7b 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards e7a8e839f6 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 6fb804b3bc 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 1161910e86 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards fff8ea1c50 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 8a84aab4b7 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 71562a6675 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 2f25d0e42e 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 7c00d5073e 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 2a67a3cdf9 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards dfb3da9d78 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 31b930eb26 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards a46977e1a6 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards a9310d5616 235: onsuccess: #2483: 1: Success after linux: 108 commits new 06e723120b 235: onsuccess: #2483: 1: Success after linux: 108 commits new c99fdc63d7 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 1f50b5f9ac 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new b2c0fd7763 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new cc33d6a555 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 8e1bec74cb 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 6d51db07b4 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 37abbe17b5 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new d6887e48df 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new b83104d2f7 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new c176390db9 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 1a35bc7569 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new c784262ed8 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new d26e1e64ca 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 8ccaf322d2 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 48ca287750 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 8075e08de1 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 0620c3a31c 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 2f6eca4523 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 199163498b 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 76a276deb7 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new a3f07465fd 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new b396d2dba7 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 16fe00ab38 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new a5e58530af 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new c5c2c7066c 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 9596106cb3 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new e15ee828c1 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 68d4ddda30 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new b30b3a3c41 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 9383c4cfcb 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 47fa4aa0ac 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new dd26013306 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 9bfe05733a 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 6087cf22d2 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 063fd898b6 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 0c2943e2a4 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 29ea24b459 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 11b987768f 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 96abe7da29 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 1f0c95360b 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new f95f060276 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 63fae85da4 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new a7cc87ac4d 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new e6acc3ffcc 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 72f2d8fc0b 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 48233a0a54 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new bd88715749 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 52263ac7fc 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 87eb233f5b 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 0211ec041e 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new bffdbd4b70 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 8d0d2e9565 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 77db83544e 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new f11e4bd850 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 7f80bffd89 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 740995a93c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new ee7df058f5 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 17d1420638 293: onsuccess: #2542: 1: Success after gcc: 5 commits new a4a4455796 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 0db33d68fc 295: onsuccess: #2545: 1: Success after linux: 10 commits new 9aba929908 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new ead40c5332 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 9b6f42460b 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 6de5dba534 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new dfc924a612 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new c5a80539ce 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 8c68598791 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new bfa2bd4699 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 20aaafe371 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 2925bd0bd8 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 79d1c4df22 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 2e3a3eba60 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 26a613e4ec 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new c73aa74ad4 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 90a4656b21 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new ee82fdca43 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 0584e0b1e9 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 059b6850e4 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new d7b97ae2f9 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 9f5da206f3 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new e16dd1e228 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new f706c97b09 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new c9589e5a5c 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 0c9c1e933f 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 9dd0848cbe 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new cac1caa261 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 24f27c2c89 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 277d7b46f5 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new ab7bd417c4 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new c9f3709828 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 663e6e6407 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new d91eb14564 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 513722c5e8 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 574e54dcd3 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new f7391351b1 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new dc5d3feda0 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new bf7743aeb9 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new d32127812b 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new a1b0105028 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new ba4c3c8cfa 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 78ae2eff09 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...]

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 (1a6dcb8832) \ 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 1760 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31968 -> 31756 bytes 04-build_abe-stage1/console.log.xz | Bin 73368 -> 73068 bytes 06-build_abe-linux/console.log.xz | Bin 8736 -> 8744 bytes 07-build_abe-glibc/console.log.xz | Bin 245656 -> 244968 bytes 08-build_abe-stage2/console.log.xz | Bin 204648 -> 204136 bytes 09-build_abe-gdb/console.log.xz | Bin 39300 -> 39060 bytes 10-build_abe-qemu/console.log.xz | Bin 32484 -> 32872 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2812 -> 2724 bytes 13-check_regression/console.log.xz | Bin 7132 -> 6184 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 17 +- 13-check_regression/mail-body.txt | 116 +- 13-check_regression/results.compare | 54 +- 13-check_regression/results.compare2 | 87 +- 13-check_regression/results.regressions | 54 +- 14-update_baseline/console.log | 62 +- 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 | 118 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 54 +- sumfiles/g++.log.xz | Bin 3402424 -> 3429556 bytes sumfiles/g++.sum | 44 +- sumfiles/gcc.log.xz | Bin 3040476 -> 3044636 bytes sumfiles/gcc.sum | 4220 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1037496 -> 1047844 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214572 -> 214616 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432144 -> 437092 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 2392 insertions(+), 2500 deletions(-)