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 e0b74b1420 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards 27a04b03f9 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 678ab6f6fe 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards e4e9a1cec3 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 8f41506334 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 6eb9b4ed37 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards a79bb6f3b2 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards da8976c8d5 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards c4d2825e24 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 9f3e4bc3f8 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards cdd4cd4bcf 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 209d69f76a 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards c25bf69107 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 320a2bde8b 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards b930897079 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 95e12d6f90 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards e91896697b 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 6e79a10c4d 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards e6e369a959 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 1a1c8f72a5 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 15cb0e554a 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 69a31189b8 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 6f87aefbb3 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards cfcca2fe2f 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 19eff5ffc0 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards abfe84a52b 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 1b46ca4be1 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 50a0c9d001 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards fb52b49154 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 8e28e730d3 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 05d0e50b2d 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards f7dc149707 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 911907ba3b 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 4f41b8eb25 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 0d02805267 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 6426851bd9 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 1a0c099085 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 69073c12f3 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 3e0a0ab574 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards da85cfd8f7 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 510774c7a4 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 4ba72419a0 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 8146219350 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards ba44388be0 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 3c3790b2e5 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 8bf1519325 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards f3a6621256 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 8149e671eb 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 733008d2d9 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards d82916ba41 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 691aef7bf7 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards dd5f962203 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 9e1d929521 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 3c8ccf50d9 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 3d5f40881d 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards ef616b5c26 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 515c1dfd3e 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards a8b41310fe 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 226e64f4ee 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards f2eb118a3c 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards e213b89250 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards e7ab4be416 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 5f7f4e5547 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards edda5284bf 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 298e06c616 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 6c84614d51 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards fd43f9224e 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 659ea589ff 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards c4ddeddac5 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards d480151157 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 79263015b4 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 3ec6787ea6 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 695c9201e2 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 1d70625d75 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 3a8b8dc89a 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 996eeb77c4 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards ad177f519e 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 6a7fe6712b 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards c8aa322b82 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 59ed6fb361 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards b9df869e9f 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 6a9653e738 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 58204fec9d 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 042555e792 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 753143b4e3 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 650146d7c2 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 99b019b7bb 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 2bd4274c39 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8adecc3bf4 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 2c20498f71 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 8beb81ab4b 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 0072761239 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards c6d605ed80 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards f3f67b22f9 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards b42472a7cc 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 3e48c5ecaa 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 26b1103e8d 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 23c9821ab9 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards b95fb9d75d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 5d15cd8860 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9e4bfbe388 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ccd3f0ecc2 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8629e193d9 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 65ca128afc 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new b7974004f4 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 7e752020cc 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 51cc57ec13 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 971e4149f0 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new fe710e93ed 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 508fa6a451 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 0775d22207 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new a5a422dcb1 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 3bddda2518 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new acaf0c5f7e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 14bbb72dce 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 28455f1bf0 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new dc996d1964 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new d8f4ea7a1c 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 61a40b79cf 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 08cd48ef31 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 2ac8372764 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 913676a0de 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 8639163402 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 3b03554fb8 101: onsuccess: #2130: 1: Success after binutils: 81 commits new a097e826a9 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 8cec83cc56 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 560a19a62e 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 0dc0726766 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new f9121bb434 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new d0a1eccdcb 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 42a968ef93 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 33eeb5bff9 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 6cb2dd28c0 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new f0b999c8ac 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 4027501687 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 3d69e52ee9 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 9d23c68f12 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 1f57b0a7e9 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 30b91d4353 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 7eb6ac4e9b 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 304ae489e3 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 043663f30d 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new af4c2229fc 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 00d1f747cd 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new e0c58e1613 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new d8a14fc173 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 36372f1a2a 124: onsuccess: #2159: 1: Success after linux: 23 commits new 110c03f9aa 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 808849064a 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 9133fa3a5f 127: onsuccess: #2162: 1: Success after gcc: 9 commits new c8eb7a82ac 128: onsuccess: #2163: 1: Success after linux: 23 commits new be7f7a0537 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new fe9ac06d3e 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 1d24009fa5 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new bd2363b5f9 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 6884700a56 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 33158c8b0e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 131068fd79 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new f6d0100305 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new c0bba27ded 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new d5feff19ad 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 0e01eb92dc 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 71216323d2 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 34eddc4bb3 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 6e2b53c280 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new c622c10288 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 61e8ceda6e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 7918b94d88 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 3e175b18fc 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new b6e8fbb567 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new fad5c53acb 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new ff039a889a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new b52c847998 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 7b8b528b92 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 179c332ef0 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 2a2062d213 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 6512c13a40 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new c77e1ccb46 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 4661598829 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 630cb522cd 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 79db62ddb8 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 1a3d86db7e 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 6686584975 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new ea9b0e6a18 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 2e75ab752f 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 26653cee21 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new c242a7adb7 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 51565caee4 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 50cf8c3a15 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new e2bb80b4a7 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 22de9b460a 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 74cfa6b1b3 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 9ab627b4c7 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 04d6c0cef2 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 05d156c474 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 46e3d848d7 173: onsuccess: #2208: 1: Success after gcc: 10 commits new e608eb1bc7 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 4422cd83f2 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 7bf376107a 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new fdcf8cbd03 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 0f8ee11b16 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new a24eae5c79 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 374433c471 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/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 (e0b74b1420) \ 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 1752 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30312 -> 31020 bytes 04-build_abe-stage1/console.log.xz | Bin 72372 -> 72812 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8792 -> 8812 bytes 07-build_abe-glibc/console.log.xz | Bin 240016 -> 239588 bytes 08-build_abe-stage2/console.log.xz | Bin 203380 -> 204876 bytes 09-build_abe-gdb/console.log.xz | Bin 38580 -> 37984 bytes 10-build_abe-qemu/console.log.xz | Bin 31980 -> 31692 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2736 -> 2860 bytes 13-check_regression/console.log.xz | Bin 17588 -> 7660 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 88 +- 13-check_regression/mail-body.txt | 244 +- 13-check_regression/results.compare | 312 +- 13-check_regression/results.compare2 | 2076 +----------- 13-check_regression/results.regressions | 160 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 4 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 246 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 160 +- sumfiles/g++.log.xz | Bin 3420352 -> 3434820 bytes sumfiles/g++.sum | 196 +- sumfiles/gcc.log.xz | Bin 3006288 -> 3024176 bytes sumfiles/gcc.sum | 5326 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1031720 -> 1034648 bytes sumfiles/gfortran.sum | 98 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202996 -> 202680 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2696 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 429380 -> 421780 bytes sumfiles/libstdc++.sum | 10 +- 44 files changed, 3661 insertions(+), 5406 deletions(-)