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 10e4a978e4 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 07a0d311c6 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards e8bda3ba82 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 69431f5ef4 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards cd19e7828c 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 4957ef8385 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 272df98706 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 5b6f8ba44f 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards f67cd69d4f 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 933d6ad453 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards a2afb7ac93 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 0d3fa36778 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards ef78aab65d 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 6179b2a502 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 4e6d068965 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 4e294ac9c8 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards efbe4f7e94 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 5955e62660 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards f5a9d04c68 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards b7f9cc97cd 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 1e0535fb25 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 9ccf7f7908 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 9ee24560f8 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 3f70697a91 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards f5af396d92 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 6f03b48d83 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards a2fdf5a0da 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 1f29431547 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 1b298494e5 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards c25de42812 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 32bead8edc 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 41725001ea 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 1d9b72a96f 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 1608e615d6 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 4611460c33 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 5383f96531 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards cf9fe84535 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 501afd88b4 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards d1075d975f 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 22cb6dfd0c 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 821970efe0 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 6b1f924046 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards ce633f97fd 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards b84e0b747b 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards fcabcae4f6 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards d445d42367 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 1b5fedc2b3 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards a5d75c7aed 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 103f392b15 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 4f40984576 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 2d4db05b3b 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards c189f625bb 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 29342f5c15 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards d3f9ce7620 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards b9d8642517 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards b699c9c5a1 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 08cfe6b594 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 0ea75a1c5b 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards aa81b4b626 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards c84cc122a6 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 876c0ee003 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 4e007b2f97 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards b5f0ba151d 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards d8d119a8f8 301: onsuccess: #2118: 1: Success after linux: 16 commits discards b2bb01d0d0 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 594392e087 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards b5b527e53d 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards cbaec1e99b 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 381ea76fc5 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards c94f08c93d 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 9845db5c91 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 2dbbb52f9c 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards de15ad6faf 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards ca09f800ac 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 206e27727f 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards a7219b7838 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 8a604ac689 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 78fc935055 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 523a0ccae2 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 54967dcd57 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 1928402e83 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards eb80695bcc 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 4d6bfe67c9 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards f4d04720d0 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 64ddca2ac7 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 33e1f6b226 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards f79bd6fb1e 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 4ff3952a55 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards b6a33cacac 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards faaf511f2d 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards a2a2525502 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 71d78011cd 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 8b95298f0c 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 22f497313e 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 219146661d 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 356e739740 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards b005312033 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 451d258ea1 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 6c20218442 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 725babf9c1 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards bc90b94c7a 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 3c2a8d700b 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new b4889f05ca 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 6463a40d56 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new a5ed0aa61c 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 10a9084913 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new bf89e7ccee 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 66252650ff 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 8e08ab9daa 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 1fefb8e420 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 4753129477 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 160ffaf875 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 7f6c71c01e 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new c99bc181e5 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 166530cce6 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new b7239b0025 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 39d4ac335a 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 42c0463e55 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 0dffc6f951 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new ae97c53251 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 0d25f781e0 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new a6d1d1c77a 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new f8c49082ef 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 8868eb626e 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new d04638506d 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 2684160d27 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new c559d78c35 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new d75222e267 290: onsuccess: #2106: 1: Success after gcc: 2 commits new fbab153259 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new e2c42ac4cf 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new b9bcd98699 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new c9d63e4458 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 9d045c3bf0 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 7567290b0a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new ec5467a39f 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 727be8869b 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new e519c5fac7 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new d11a4aa31d 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 8ada9789a1 301: onsuccess: #2118: 1: Success after linux: 16 commits new 55b76d548b 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new be2564f47c 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 11cabaa48e 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 31cdda059d 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new bd7a316631 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 45f5e58ece 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 907d8377ba 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new b53602f8c4 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 8d08998eb5 310: onsuccess: #2129: 1: Success after binutils: 4 commits new cd4af6949f 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 42144c0ba4 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new ab26756596 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 694e9c6663 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 236b8c07f9 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 8466efff97 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new c236e65d11 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 6e263250b2 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 06ba1ec313 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 6e09cde9f6 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new f6e89fac9e 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new fd7fb263f3 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new c91c893a79 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 6f314c6b3b 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 9abeb1fa89 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 07b4d2d102 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 4ac3cf8e08 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 51650cce3a 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 109a17a70b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new b4bb57a4be 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 967305c287 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new b2f0524ad6 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 4508d531fe 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new ee23b73815 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 6443e6cc17 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new c040a0c0e1 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 7a1f83448d 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 29a61794e6 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 372cfda514 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 0b72214d06 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new ad05e4579a 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new b86fa52a89 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 0c9c7eefcb 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 2c36614c11 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new b3ff3834f6 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 3ee4fbe6bc 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 8c8bfe1c92 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new ed96c590c9 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 8c327c5f10 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 28134f495e 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new d686eefd19 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new c39d6ebffb 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new f22fe2054c 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 5b8c27e5e5 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 883043bcf1 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 328491ec13 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 37fd69f877 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new f9f9b67d1b 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new ef4596611b 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new fbe98b8660 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new c66f8e4bc7 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 2b04a22fff 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 110752fc8d 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 8dfc797e76 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new a52b1f66e2 365: onsuccess: #2185: 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 (10e4a978e4) \ 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 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31024 -> 31568 bytes 04-build_abe-stage1/console.log.xz | Bin 91936 -> 93708 bytes 06-build_abe-linux/console.log.xz | Bin 8712 -> 8732 bytes 07-build_abe-glibc/console.log.xz | Bin 235904 -> 236924 bytes 08-build_abe-stage2/console.log.xz | Bin 228488 -> 230344 bytes 09-build_abe-gdb/console.log.xz | Bin 38384 -> 38816 bytes 10-build_abe-qemu/console.log.xz | Bin 31644 -> 32380 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2800 -> 2992 bytes 13-check_regression/console.log.xz | Bin 6764 -> 14916 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 9 +- 13-check_regression/mail-body.txt | 62 +- 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 2124 ++++++++++++++++++- 13-check_regression/results.regressions | 38 +- 14-update_baseline/console.log | 66 +- 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 64 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- results | 38 +- sumfiles/g++.log.xz | Bin 2656180 -> 2645804 bytes sumfiles/g++.sum | 917 +------- sumfiles/gcc.log.xz | Bin 2200772 -> 2199040 bytes sumfiles/gcc.sum | 3488 ++++++++++++------------------- sumfiles/gfortran.log.xz | Bin 894228 -> 891272 bytes sumfiles/gfortran.sum | 100 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214020 -> 213972 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433440 -> 435840 bytes sumfiles/libstdc++.sum | 27 +- 45 files changed, 3770 insertions(+), 3275 deletions(-)