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 424566614d 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards bd83b40d88 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards 55b014a46c 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards e072006caa 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards eb02b6d615 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards a9991900b7 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards 98abe9c6e2 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 114694e3d7 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards 71d38b19f2 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 415eb89798 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 77c4615c32 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 3ea9a2d242 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards d47bc10531 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards ca7d83cb3f 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 4bfaaabf6b 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 9de7b61075 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 50d78ecbb9 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 999cdfe0c1 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 2c45851f3f 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 581f1fcad8 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 21e79379cd 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 294a9a8015 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 3717ac21b8 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards ffc178437f 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards ee28f32e72 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 8e9f1b80d3 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards cbfc29bf10 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards b4bc0951c1 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 06c3ccef00 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 45572fbf30 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 61d0545c02 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 33cf0cf06e 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 77c7de0d54 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 11f5d9d233 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 890f0c2737 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards e2f282c55a 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 50f7eda463 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 2a74db9604 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards da004f8a61 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 01b4d47c70 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards f25d0ba190 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 3236220317 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards a3bc8b8fdd 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 631450ff14 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards c832808e84 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 5ea881a9dc 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 67af99a87c 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 9117e97318 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards f3c2cbf0aa 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 91d2059555 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 7b445eb040 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 331784fe7f 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards fdd6f965ba 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 47e3cfa17c 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 0b9ba2ec45 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards b7ca2d8912 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 9669aec0e6 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 064a312371 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards d0eebe68d1 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 382b816fe0 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 0191968ca5 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 3eb671ca21 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 91256d2311 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards b2ea12829a 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 8859f3d70c 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards a07ac54266 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 523641b3e4 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards efe79b176a 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 367c37f94c 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 5615ba2559 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 656a8a47c6 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 69999c6b6b 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 6f26350854 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 45fd510a66 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards e793b1b8a2 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 0c25c6bf58 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 4e41594b2d 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards ea0c8fc8bf 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards b87165eb5d 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 549c8c31cf 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 95a7f3d463 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards e2dcca9bcc 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 55531be0cd 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 1863aecd67 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 9e1d783ef2 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards c7e77a4046 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 55a8d83f54 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards a6ad27878f 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards f725b800e8 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards eea14937e1 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 3ad577a5b4 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 703645fed4 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 9fae6d5251 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards bbf18fa9db 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards a5e878d0f8 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 521867fc4d 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 11ae719a38 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards fd8392d4a9 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 41eeafbd63 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 399cacd759 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards adb4f48a49 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 4507fa061f 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new f735c6e9e3 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 259c61cb01 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new e89894d2d5 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 4ed80b9955 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 8dd8db0254 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 634690f346 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 61c480011b 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new b374adc352 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 9fc0074482 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new e8abfd1b6c 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new f0ad8a6b52 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 3225e0f479 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 4c16159a84 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 00638abf08 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 9573cb4b78 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new b5289aecce 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 3d19c22599 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 97daaa84e4 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new bce002a9c6 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 1df2de506e 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 349d6308e2 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 23e6c43351 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 3f5d85c2fb 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new f1bf018051 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 4f9169c8c9 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 93e90a02c8 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new fad47fdae0 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 46aadb94c2 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 4ce3a126f9 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new dc9a86df5c 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 0fe853bb3b 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 4ee80b7cd3 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new a1b623a956 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 6abacc86e7 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 8add9d2814 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 3a533a5480 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new e72ba8bc2b 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 497641fb66 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 67b2280cba 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new f446499de3 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 6ce182d239 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 237f4fd899 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 811e6770ce 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 038107bb0b 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 6f3623a2cb 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 4035cfcd1d 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new e1e81d1076 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 546aec3a96 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new d504828bfa 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new cff114f783 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 0ae535f94d 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 5a2ec81c34 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 1afdb7387f 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 79ac79d2eb 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 374e14f265 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new ba0324df06 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 22c5b9b275 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 1eb910f4ce 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 1c08d72882 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new c170b97107 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new f999009d0e 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 284f9ae1ae 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new f60a808990 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 2c7c1cbf1a 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 1398427ff1 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 38239d5b39 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 2c8f75ea74 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 18b79749ed 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new a3b766c8c4 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 29119cf1b8 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 1754638ecf 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 723c7e7b22 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new e90631a09a 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 6c7eec9cc4 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new cfb4f5140c 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 0ee36ddec7 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 045fce3ef7 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 52063c5d10 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new d1e02b11b1 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 908f7811da 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 95253b98e4 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 107f029008 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 4a152fd337 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new eabc0a25b6 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 0aff431aa7 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new af3d96d8f1 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new ed9e4540d8 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 3da459e270 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 00a9908f35 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 8356a97bed 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 39f3857e03 408: onsuccess: #2662: 1: Success after linux: 11 commits new 9fc5211d8e 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 7779a7248c 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new f282e48b4f 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 36f323511c 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 051b4b00e2 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 46bd6024f5 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new c05c9fbdb2 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new aa71a01918 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 2873a4638e 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new 99e771c653 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...]

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 (424566614d) \ 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 1776 -> 1900 bytes 02-prepare_abe/console.log.xz | Bin 2808 -> 2816 bytes 03-build_abe-binutils/console.log.xz | Bin 31312 -> 31720 bytes 04-build_abe-stage1/console.log.xz | Bin 71580 -> 72008 bytes 06-build_abe-linux/console.log.xz | Bin 12952 -> 12948 bytes 07-build_abe-glibc/console.log.xz | Bin 244176 -> 244120 bytes 08-build_abe-stage2/console.log.xz | Bin 204520 -> 205084 bytes 09-build_abe-gdb/console.log.xz | Bin 39352 -> 39300 bytes 10-build_abe-qemu/console.log.xz | Bin 32396 -> 32272 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3848 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2700 -> 3252 bytes 13-check_regression/console.log.xz | Bin 10208 -> 8648 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 150 ++++- 13-check_regression/mail-body.txt | 159 ++++-- 13-check_regression/results.compare | 162 +++++- 13-check_regression/results.compare2 | 938 ++++++++------------------------ 13-check_regression/results.regressions | 113 ++-- 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 | 161 ++++-- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 113 ++-- sumfiles/g++.log.xz | Bin 3401324 -> 3410744 bytes sumfiles/g++.sum | 14 +- sumfiles/gcc.log.xz | Bin 3028148 -> 3045568 bytes sumfiles/gcc.sum | 254 +++++---- sumfiles/gfortran.log.xz | Bin 1040516 -> 1042780 bytes sumfiles/libatomic.log.xz | Bin 2296 -> 2312 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217768 -> 217388 bytes sumfiles/libgomp.sum | 10 +- sumfiles/libitm.log.xz | Bin 2660 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432072 -> 438724 bytes sumfiles/libstdc++.sum | 308 +++++++---- 41 files changed, 1320 insertions(+), 1180 deletions(-)