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 9e128dfb1d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 3e203eadec 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards cc52cae589 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards ac04ce9b67 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards dd7b09d863 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards eaba73e4a9 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 6e680e5ea2 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards fb6cb3687a 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 9531e861b0 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards b695e5b309 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 6e68d68638 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 7f37eeb583 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 53629bd16a 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 171618c649 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards d1efbe57b9 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 4273b684ef 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards a7f2dc7fce 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 40b0426105 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 0e0f81d27c 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards bcb69ecb31 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 7c3a38d2d5 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 0a6c77d086 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 5e08b11f6c 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards b6b174e821 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 98b8367ac2 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards b49337e359 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards dc5a84e171 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 962bb9dcc3 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards c379783704 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards aafabfbe63 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards edd9c2d743 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 534df12109 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 399d09f325 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards b39a2592ef 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 089ce1f8fb 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 9fb38914e7 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 2f132ca0a9 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards ff11d5969b 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards f27be58431 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards fd51fe565a 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 2b30956a82 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards c30bbca6f7 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 46ec374db8 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 3680acd75b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 79bb6f81bd 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 0019016d02 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 2f6c5fd82b 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 012023bed3 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards a56f5138e7 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 7b137bd039 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 78ad2426ce 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 5e1a66d796 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 7bc421affe 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards ee15fdaf19 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 3b8008e29c 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 9efb7fe2a3 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 7d1f78eac0 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 43af303bc2 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards a6dead0b67 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 88914767d3 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards ed6cd045e5 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards a6780cf512 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 0b3ed9b1cd 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards a43c440b40 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards d40549424a 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 84b59f4842 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 995f11b961 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 11061d205d 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards c1ee2a1da4 301: onsuccess: #2118: 1: Success after linux: 16 commits discards b1ea81db4f 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards cf76b2d6f4 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards dde910b63a 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 2ebe0daae5 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 1202f93cd5 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 48352f0df0 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 72e7d77e74 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards bbc2536fa2 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 603a9612a8 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 589ade4967 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards de7cc53c1e 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 418b026a95 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 6808b794a3 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 3eb356dfa3 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards fe383c5621 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards a8cc5ee671 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 4e8fb8dfbd 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 9fa7be692d 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards d28ee74348 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 5cf86ee597 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 7409a1a147 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards c095f47b1d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards f642c1e916 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 7a0bf9444c 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 0f529b6415 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 33a0871357 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards d1f600669e 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards c09850e63b 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 281a66e60b 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 3e6757abe5 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards af83d5e449 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 22fad42fe7 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 109b1bd320 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new a150ab7ef5 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new ce76c47a26 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 483e85e1eb 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 5b6a10a286 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 13c75ddcf6 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 870e00bbc1 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 7dafae749b 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new c8d0d05056 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 48798fbdb6 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 87aca9cea4 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 6c37f0f4bf 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 4334d8cdd1 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 5cea89f563 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new bdc137157f 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new a0132e30b4 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new ac374325f0 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new f9a6ee842e 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new cabbc9a3ae 287: onsuccess: #2103: 1: Success after gcc: 9 commits new bd4e0da4a5 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 7c6ca3ee01 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 85f244fda6 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 8644921aa9 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 25080d09de 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 79e04cfef5 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 2af82b6841 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 3770bb5a12 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new c6381b9c33 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new f09b1da2a4 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 42d5c026b5 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 5ac577d7d2 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 4a1ad81e3e 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 8504541a2a 301: onsuccess: #2118: 1: Success after linux: 16 commits new 9c04c7827f 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new bb18a3270f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new c45adf420b 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 39c9b8f7ab 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 1ccc2fa433 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new d393fc64f5 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 2075c07f5b 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new c24d3854a6 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 53a1e7a884 310: onsuccess: #2129: 1: Success after binutils: 4 commits new eaaee8c5d0 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 3629798d62 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 3bdd9c7218 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 4df5cd8aba 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 8dd9322883 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 3a9a13ea57 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 7ab71db63d 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 41cd48017c 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 8cafb3d230 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new dfb105dd11 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 38dafaf07f 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 2170c59c66 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new b496f712ba 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 6dcddf4bc2 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new dc392f7213 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new bfd3fa5685 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new b52b824e90 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 06698d552b 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new f2650f8fa7 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new e4d2dded1a 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 1293891fa5 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new e60ad6f06c 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new c84a02832d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new cfb6061b0f 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new cea9a237e3 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 6a8599f4f5 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 02547880ac 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new d36e624027 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 4eba5f09f3 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new f7f4d3d823 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 40fc6ee1d7 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new b8366dc46f 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new e6b429420e 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new c7a0b55b5e 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 638ae9bc39 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 58acdb16d4 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 286943cc5c 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 461a0beee0 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 31e01799d9 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 2cc971e74c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 67c2085ef2 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new f26bf6b5e0 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new dec6621d19 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new c372256a94 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new c7e38b961a 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 5af537bd23 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 795e53e8c4 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 83c39bf988 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new bbcc297f7a 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 965d156189 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 6dbd0d1f15 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 540a005e9b 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 8e2aa1ea71 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new a5b9b2daa5 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new adfff57ecb 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 15672265cd 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new cc8057ea09 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 5f88c11ac8 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 785a843632 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 1b2b32c3f8 370: onsuccess: #2190: 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 (9e128dfb1d) \ 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 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31524 -> 31420 bytes 04-build_abe-stage1/console.log.xz | Bin 92288 -> 92824 bytes 06-build_abe-linux/console.log.xz | Bin 8560 -> 8672 bytes 07-build_abe-glibc/console.log.xz | Bin 238652 -> 237268 bytes 08-build_abe-stage2/console.log.xz | Bin 229664 -> 230788 bytes 09-build_abe-gdb/console.log.xz | Bin 38340 -> 38792 bytes 10-build_abe-qemu/console.log.xz | Bin 31092 -> 31068 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3928 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2784 -> 2956 bytes 13-check_regression/console.log.xz | Bin 6888 -> 7620 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 14 +- 13-check_regression/mail-body.txt | 62 +- 13-check_regression/results.compare | 21 + 13-check_regression/results.compare2 | 126 +- 13-check_regression/results.regressions | 21 + 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 64 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 21 + sumfiles/g++.log.xz | Bin 2642944 -> 2644360 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 2229072 -> 2228360 bytes sumfiles/gcc.sum | 2347 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 891436 -> 896764 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2268 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214232 -> 214184 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 445396 -> 444032 bytes sumfiles/libstdc++.sum | 51 +- 44 files changed, 1514 insertions(+), 1375 deletions(-)