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 ce1c0e0076 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 87e11667ba 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards d1bce3a33b 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards c43cc55ac6 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 635e57f814 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 00d39cf276 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards a55124605e 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards bca2449645 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 4f62bf872d 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 769410efc3 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 292b41f489 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 550d80647b 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 5e05070bd5 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 3a935be05f 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 0559ac3a72 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 9c280b8be4 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards e934c21682 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards b1f46c90e7 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards dd98b60c7a 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 6c20283c34 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 63aebc8293 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards c0df59d6a0 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 02dc0b41a2 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 0177f61f0a 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 7f0b1d6e48 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 4ee4bd64fe 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards e2a1fa9e42 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 23a5371bb8 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards adb4a78e98 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards f7e73fcb09 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 452ca3e992 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 115cbc8fc8 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 57c6f108f8 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 6c941089a8 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 73fc4f8b21 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 18d2219603 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 9920e2bdcf 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards b09f9263a6 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 75f0bc1158 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 86ca7a4d78 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 8bb15b5cfd 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards ccbc56fab3 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 8c1cff074e 295: onsuccess: #2545: 1: Success after linux: 10 commits discards f5c1fbe5ad 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 97bca52a9c 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards bb44803da3 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 63eeff1ede 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards ec056261fb 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 493b8f2eaf 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards c0c09d89f4 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards a14c05754c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 84233200cf 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 0c782363d6 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 5a3fb2a580 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 3aec3908ee 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 75d90abd0f 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 539169f31a 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 3512e93078 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards d35ca24184 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards ea8eac640e 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards ee42bd3111 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 204ad9dbbd 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 88e0050fdf 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 883e1319c4 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards e1329c2637 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 7811a8aa13 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 6e76565a76 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 9b24ce4d8b 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards db9e26347f 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 2c9bbfa093 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards be4da7ee47 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 1d1d0c9ed5 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards db578093f4 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards f6fcb82531 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 8e27e95551 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards ef93251299 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 5c427550a5 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 7665c2008e 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards aa250a9e49 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 623853804c 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 2d4f401eb0 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 666bd5a19c 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 23cb369445 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 0064169ffe 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards da3a571654 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards e9396644d8 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 6ad7e3b8cd 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards dcaa174298 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 71b39bb08e 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 72a068fac1 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards db49320755 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 167e925572 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 2eda285396 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 9aeab038ba 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 0f6bfb5666 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards c68ea632f9 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 0256c789bb 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards aaf30ba5fb 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 6a311518cf 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 0df449ccdd 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 9028f7e360 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 335eb2cb4d 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 766a503b4d 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new d883cfcb71 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 9822a725df 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new c9dc1399a8 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 7c814e6958 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new c848eb8beb 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new e2abdab924 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 86b8c03caa 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new cf786d0db3 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new d392c9058a 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new dce6bc06ca 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 7552a72abf 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new b648c9c220 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 504c41cd5c 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 2473baec22 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 9dccd679d6 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new e3fabe8ae3 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 090c7492d7 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new e9d76e8339 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 81de44137e 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new f9146506e1 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 5959d9f913 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new f76141ae25 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new c8e865b5a7 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new d7430bb107 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new ec50eb9686 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new dba38031f9 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 60aa962c06 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 6a2308efa3 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 4f6e12428f 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 4a458be42d 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 97207b2529 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 8777e6d118 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 1e5cc062c1 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new b6c94d9438 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new df133d8e21 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 95029bf5d4 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 470d7e70d2 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 251663d8c0 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 72a6de6f81 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new bc3b316d48 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new bd7e887148 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 2f83e5bb56 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new e941a1f4e7 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 99835ef19a 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 1d17e4f3dc 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 48ea558d81 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 9fc686effe 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new e23718dc41 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new d47e71754a 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new edc559d059 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 505d98bb24 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new ed42dffe38 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new d194c2ec4c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new d243f62c78 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 639f68c725 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 6b686324bb 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 1c470ed013 295: onsuccess: #2545: 1: Success after linux: 10 commits new 8ba11a2d96 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 18a5af8e0a 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 533faaea22 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 090667d07c 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new e160919b93 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new dadc9b3515 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 3ad48d6084 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 54b294cd88 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new b06a071e67 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 48dd8f2ed5 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 119559533c 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new a3e85d4773 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 69f501cbcf 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 76734f3962 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new be564dac49 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new ee33d10fdf 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 2d4c3cf2b5 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new da14a7ccec 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new bdaba27326 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 9e380eabc6 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 2f7f4bdb94 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 007278768f 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 3c5174e9e8 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 6f46c99691 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 64517a249d 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 86f1ded720 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new efff9a2147 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 5c70102278 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 93e34f0bbc 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 69101e9480 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 9734bc7940 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new fb04beb76f 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 34caf91d6c 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 913546624d 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new cfd355fead 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 84fae4c047 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 8928ea9fbf 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 36abd70b9d 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new f6ab7ca07d 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 8cbda5ad50 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new f56b4cdf8b 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 68e862c33e 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 202f4a6459 338: onsuccess: #2588: 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 (ce1c0e0076) \ 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 1792 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 32508 -> 31772 bytes 04-build_abe-stage1/console.log.xz | Bin 74136 -> 73912 bytes 06-build_abe-linux/console.log.xz | Bin 8816 -> 8496 bytes 07-build_abe-glibc/console.log.xz | Bin 247112 -> 247200 bytes 08-build_abe-stage2/console.log.xz | Bin 208724 -> 205684 bytes 09-build_abe-gdb/console.log.xz | Bin 39428 -> 39208 bytes 10-build_abe-qemu/console.log.xz | Bin 32656 -> 32920 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3944 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2800 -> 2888 bytes 13-check_regression/console.log.xz | Bin 6048 -> 7088 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 11 +- 13-check_regression/mail-body.txt | 97 +- 13-check_regression/results.compare | 49 +- 13-check_regression/results.compare2 | 58 +- 13-check_regression/results.regressions | 49 +- 14-update_baseline/console.log | 70 +- 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 | 99 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 49 +- sumfiles/g++.log.xz | Bin 3414296 -> 3423552 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 3046432 -> 3042196 bytes sumfiles/gcc.sum | 4748 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1045752 -> 1041628 bytes sumfiles/gfortran.sum | 10 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214908 -> 214756 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437976 -> 437604 bytes sumfiles/libstdc++.sum | 12 +- 43 files changed, 2631 insertions(+), 2713 deletions(-)