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 8b31d8e950 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 88d7c5ec34 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 149262f517 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 43d3be003b 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 1b42d337b1 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 6c8df03938 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards c7257fe8d1 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards b9be8e87cc 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards daead14c14 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 89c2c900fc 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards c3700e348d 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 4904f1c2b3 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 5ca150d505 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 1b9e2d1d16 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards db1d701bcf 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 637e3baa44 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards a1f85157ca 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards ab6c398f1f 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 44725bb8f7 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 439907ea7d 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards fecdc602f3 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards d0da84e4aa 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 59dc6d0292 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards a28b461365 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 2aaf68381f 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 6895086174 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards e939c14d66 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards b4ac9a8a68 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 8c644a871e 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 1dfd1fdd7f 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards f1a11e2d78 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 91b43a4f59 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 56f49415f6 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 4fa923f070 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 03aea6e7c0 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 29a9ad0bf9 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 2d3f3c5e54 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards faa0b15851 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 95b2a9f76a 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 802a689500 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 02ec5d8ed6 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards d991a7737f 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards c96e59c9ac 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards d4ed83edc6 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 23ff0c916a 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 8d7940332c 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 566a873e79 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 9b31567e82 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 9c562d5285 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards b0ea80ac9e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 57119171a2 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 44921df752 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 4eb7475902 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 4d62556218 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 5fb9a3f13c 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 724d171995 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 800a2771c3 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 41ae4d6ad6 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 0ae0094362 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 1fa2a359f6 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 71b16c72d8 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 6399cb2d5f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards e64c5fceee 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 855a4e1c22 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards c398e256f7 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards bccfc34133 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards fc191097a7 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 159747c0d0 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 53e9539f48 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 9c84d5b392 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 669cd111b3 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 75b745db30 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards e3774cf0d3 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 343610d1f0 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 8d11617c08 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards a2bb1c96b8 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 4e0251c83d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 9325ca3541 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 13d23124f8 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards f426095000 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards fc55312a9c 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 796039bb72 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 0fe69fe987 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards a3ebf52714 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 086be1a1e5 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards f79850a650 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 2ff8435168 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 987eac0aac 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 7e5d1b87bb 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 240cd79583 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards b5a5f5707b 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards a730ed77b0 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 6ba2209930 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 1155490124 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards d7c9905c08 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 4ba92cd475 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards e53f33404f 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 9d4b076846 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards e8cbbf256b 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 997fa9b412 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 197ae0cc2c 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 9fb77a3b00 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new b093fb78c6 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 76aea855be 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 6ad68ad41a 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 2c46916a85 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new a35d4d5aa1 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 6674719324 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new e98c4bcfa4 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new fc7c85422a 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 2b097d6d76 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 07598b6f4e 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 84ebd56613 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 9246697993 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 2bafcdbe8e 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new a1b5d7dd76 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new cd002a1152 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 65c982199d 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 8d37122d3b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 4a213fd9c5 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 0350e182cd 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 2801c59f7e 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new df331715c9 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 6d55919ce2 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new ecaec3d5b7 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 64b54a8cfc 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 7c29e8bbb7 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 6404ad9a99 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 65ec8b2ed9 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 5bfbc378b1 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new f52543a97b 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new a6922a0a70 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new d5f883c426 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 717f9c0a75 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 5d24ae3529 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 00423c094f 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new ca66850cc2 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 984082b85a 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 115a0b9473 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 091c86333b 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 2e5d4907f0 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new dde7512789 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 310eca8ebf 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 034bc8652d 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 1d7d03c954 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 05d635d23a 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new d093187ed1 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new ea9ea0336b 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new f6d21826ae 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new dffd1d4608 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 22e03d8a61 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new e72edc6380 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 48cc47bcdf 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 6a4a2e765e 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 87c1310529 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 5bb7a75454 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 4547c6fc14 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new bcda91816a 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 00fce40555 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new cade27172a 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new f38e7a926a 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 0ea1979bd4 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new fedea84793 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new d6c362a8d0 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new b8f765241c 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new fa82ff37a2 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 3d8d157031 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 63155e4056 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new abca45845a 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 337610b9d2 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 0366cd30ef 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 4f8f516ed3 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new c7243e8131 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 8baafa13a5 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new f4d3656b2c 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 5c17bb3f2b 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new d55dca8758 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 11a22f16dd 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new b394f8e03e 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 9e35a804cb 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 52804fe0ee 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 731aa802f0 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 4c9ba07805 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 0b27233abb 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new f92177cdd6 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new c3437d4588 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 4ebde4aee6 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 464e4a1181 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new eb6b1d5030 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new f950f4ac37 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 4b81e3103d 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new cbb0490d33 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 76c3f9493e 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new a12462fe05 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 547687e00f 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new a5dbc4f2fd 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new e39f4ebbcb 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 27415b6969 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 75efdf4182 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 52f7f1ec53 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new a6f3a55155 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 8ab7d7ca43 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 7221c3e25f 410: onsuccess: #2231: 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 (8b31d8e950) \ 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 1796 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30792 -> 30912 bytes 04-build_abe-stage1/console.log.xz | Bin 91376 -> 92040 bytes 06-build_abe-linux/console.log.xz | Bin 8364 -> 8908 bytes 07-build_abe-glibc/console.log.xz | Bin 236212 -> 236400 bytes 08-build_abe-stage2/console.log.xz | Bin 227416 -> 228184 bytes 09-build_abe-gdb/console.log.xz | Bin 38164 -> 38344 bytes 10-build_abe-qemu/console.log.xz | Bin 32080 -> 32184 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2880 -> 2628 bytes 13-check_regression/console.log.xz | Bin 7284 -> 6844 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 6 +- 13-check_regression/mail-body.txt | 58 +- 13-check_regression/results.compare | 28 +- 13-check_regression/results.compare2 | 84 +- 13-check_regression/results.regressions | 28 +- 14-update_baseline/console.log | 66 +- 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 | 60 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 28 +- sumfiles/g++.log.xz | Bin 2649560 -> 2650768 bytes sumfiles/g++.sum | 12 +- sumfiles/gcc.log.xz | Bin 2190764 -> 2213672 bytes sumfiles/gcc.sum | 2278 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 889020 -> 894548 bytes sumfiles/gfortran.sum | 13 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217108 -> 216840 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434352 -> 442152 bytes sumfiles/libstdc++.sum | 37 +- 43 files changed, 1414 insertions(+), 1344 deletions(-)