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-arm in repository toolchain/ci/base-artifacts.
discards b05293c3c4 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards a9ebffa28c 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards e8ccfb51c6 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards cdb25412de 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 01652a6d79 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 2240252ece 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 10be443e2e 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 9aeb87852b 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards c5ce3b5159 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards a061bc08c4 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 9d462d3e15 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards c569eef104 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards d65c97313f 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 40a270d776 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 5030245ef9 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 2090b1a8e5 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 51ac9f8b8d 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 098eea23af 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 551e3a7f7b 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 00dcfb3797 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards d1aea38346 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 9bfae5c5dc 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards fa0d036f97 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 5250d26317 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 40d8545ef3 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards c26d7e7812 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards c81d15b795 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 24042d064b 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards a767244033 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 276d0a9bac 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 95255b7cc7 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 3055558f1f 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 88918dd752 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards cef83a6a82 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 26bb3ecd84 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards b98356da29 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards fde5c1b319 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 0c00bf42ff 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 0bc4e97b0a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 51d96109b4 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards b429f0f0ec 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards f111caa4c5 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 749ea928db 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards ec51bf4f53 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards ed739b7eb3 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 9de19d42d4 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 1d02301729 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 901179aabf 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards f42bab325b 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 79917a5d97 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 25713ce4b2 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 5e92937843 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards dc32113e2d 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards f0906c0f7d 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards d71bea8c9d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards eabca8c748 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 1ec0817092 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 7eff4b567b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 73bea9fe20 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 816b39ecf5 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 781f7e889b 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards eb9cc38c66 301: onsuccess: #2118: 1: Success after linux: 16 commits discards dcb0717fba 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards fc17a27dee 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 6fab1b478b 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 3dbca187a5 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 8b371e11fe 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 55f9475753 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 7d737482c5 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 5e105f982d 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 549bc6ea29 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards be7a2e6d50 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 9f7620ae1e 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 208ae6d9d4 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 7d05c15c16 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 8373e43f0f 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 374b592d11 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 113cbafcc1 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards f2c3c11788 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 14deeeb4af 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 954bc5d07c 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 6da0eaf27c 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 7dac83fb71 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 1e3058b9ec 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 8491f947da 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 706ef57655 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 7f4588d8d9 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 9778a320b1 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards d1cea08737 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 82ad9d3fee 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 96683664d4 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 64b7b5e22c 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 3b5532ea17 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 910fda1491 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards ea3a5882b1 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 3ad047af88 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 70fe8a07e2 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 1a01ed97f9 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 93f4291a76 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards ac310d360c 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards ad2f1088e8 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 67488c4e52 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new c6c1f6f9db 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new b8897a6703 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 1712e0dcdf 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new ecacb8dbb3 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 858f19f8c0 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 7bc936ccc0 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 4665b08096 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 417211eced 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 57dc4d24d9 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new dbbef2a7f3 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 05b1d4990a 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 2a82ff1f49 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new b0c7b48363 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 189aa298bc 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new c247977a3b 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new c7b04d0669 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new d253afc628 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 6c1b7430a6 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 1e6de0cae3 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 9368922bcd 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new a4f93b4edd 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new fc003ed761 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 542bb60909 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 2e53338134 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new bcad293a01 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 1e915f6976 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 38dc816495 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new dd9be7f75d 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 5776e59c6f 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 6f471a2f25 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new a8078661af 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 206f10f44e 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 137bd05f70 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 8b5634dec4 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new cf0fb4b51b 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 1651904116 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 6340698db3 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new eaa047d293 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 562b1ff954 301: onsuccess: #2118: 1: Success after linux: 16 commits new 5b8e1a5b4c 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new c0eebb648b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new d837185bd0 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 31d406d14e 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new cd2db8ec8d 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new c772f91bd9 307: onsuccess: #2124: 1: Success after gcc: 2 commits new d8bc5612b3 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 913e56e036 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 5160cbbf51 310: onsuccess: #2129: 1: Success after binutils: 4 commits new bb2411ec12 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 48e5e00d88 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 212e824221 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 9b8d2facf1 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 03b865fa82 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new ce0a66072a 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 3382e4e2c4 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new c07cf61783 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 6e913402d9 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 721a05270b 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 8d6e8763ca 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new fc3c3e1aed 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 898b5e6f63 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new ce46c8a3d1 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 9c7eb8bfd6 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 4a0f663a0b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new be4fc65984 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 07b3c07c7c 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new d84f0300c9 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new cec9460fde 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 930813ae70 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new efa6569086 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 274029cbf6 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new d6500ce8eb 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 508fd07537 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new ccab9ac3a3 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 7516de6441 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 8262433aed 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 89c9db8683 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 2ca36d6fea 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 69a2fb1b17 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new d4e4bd2942 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 7b8f60815a 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 99183cab60 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new ffa9275f0e 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 438dfba2e6 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 651bee044b 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new d32d0a2ea3 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 3e5e10ed85 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 5a4c9d6240 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 510f075c7b 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new b7057e3648 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 09a6b56088 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 79f3317b10 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 75d99ccad4 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new caec890dc6 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new f3ebf37ef1 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new cf26ee22d9 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new dbda359b91 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new b065679b09 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new c5d2c641a1 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new fa3a90689e 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 17e1f0a90e 363: onsuccess: #2183: 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 (b05293c3c4) \ 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 1756 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 31176 -> 31448 bytes 04-build_abe-stage1/console.log.xz | Bin 92272 -> 92032 bytes 06-build_abe-linux/console.log.xz | Bin 8788 -> 8416 bytes 07-build_abe-glibc/console.log.xz | Bin 238900 -> 238900 bytes 08-build_abe-stage2/console.log.xz | Bin 230488 -> 229912 bytes 09-build_abe-gdb/console.log.xz | Bin 38880 -> 38712 bytes 10-build_abe-qemu/console.log.xz | Bin 32012 -> 31924 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3944 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2540 -> 2512 bytes 13-check_regression/console.log.xz | Bin 7580 -> 7188 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 6 +- 13-check_regression/mail-body.txt | 68 +- 13-check_regression/results.compare | 24 +- 13-check_regression/results.compare2 | 43 +- 13-check_regression/results.regressions | 24 +- 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 70 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 24 +- sumfiles/g++.log.xz | Bin 2669436 -> 2665832 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2206104 -> 2207328 bytes sumfiles/gcc.sum | 2556 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 888164 -> 891116 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214028 -> 214060 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431312 -> 436132 bytes sumfiles/libstdc++.sum | 35 +- 44 files changed, 1540 insertions(+), 1470 deletions(-)