This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm in repository toolchain/ci/base-artifacts.

discards 51a972b909e 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards f99d31b4e81 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 1fd91ef65f6 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards a2388eb7e2e 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards a583cd7badc 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] discards ac3a413b437 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 38e6b467401 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 66c15f9f90d 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards ee94ac9fa73 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards f7559731074 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 41add5933e9 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 1704156cf3b 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards fd1a27dfbce 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards 652fc17cae3 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 58eae4eaade 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 87e8d7e51dc 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 6c41fcca33f 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards dfd4ac17a8f 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards fafc7fb7ab8 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards ea53126a411 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 10c023d0dc4 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 0c1788a129d 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 1d760e24c13 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 0c72c8034ab 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards ad3f6b39b1d 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 19318008900 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards fb9f4f8db0d 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 4d90a52af5b 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 59efc369950 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards a3958af5cb9 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards c358dff2f68 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards a104cd1fd66 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards c1f00113ae8 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards d426a0135cf 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 4c2cdf2f864 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards abc365060de 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards b750d29696f 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 4034a70b6ef 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards aa528a7d455 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 8399344feab 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 506a3731a0a 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 3486f56e541 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 28e0068aa1f 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards ca8075cdb4e 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 5a8fe8cd6b8 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 28764d7b257 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 8e64d047f52 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 0d4665e70ce 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards fe311ed58a1 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards b77a5282568 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 015bfd31506 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards 5d68cef8b15 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 6ce8156d157 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 0d1a749ad2b 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards ce65531a2a5 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 996f697651b 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards bd9feb8397e 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 624278eac29 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards f250b5492a1 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 16809b6b5a5 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 1140fcefee2 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 3a2507abbba 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 5560623183d 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 91a7e759947 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 86e883c9b4c 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards df867b1f874 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 81288b36abf 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards c2b6c56c502 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 644930f8b05 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards f89d6a1fb9c 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 1d629ddade2 162: onsuccess: #624: 1: Success after linux: 10 commits discards c7e463c6c41 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 6a77f9bfd93 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 418af3d6e92 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 964e4dbf3a6 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards d87ed2c1368 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 2753396fcb5 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 0bf00103cb8 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards a76a2502ffd 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards cfe4bc04532 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards 8ecc69b5c27 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards b96839d9dbf 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 5f9333596d2 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 2260528e6d8 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 70c3372339f 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 239315a4fb4 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 2baf70be69b 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards c4464cf0eaa 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 88ca1afd8c5 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards edc1505ca6b 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 62248de7ce4 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 31f367a7be3 141: onsuccess: #601: 1: Success after linux: 794 commits discards 6001724bff2 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 7f4f985a74d 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 538a586d35d 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 58285c6674f 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 59fde2a6b81 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards dca42e17443 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 2b9d36dd47b 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 389ab66b08c 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards f9fb652881b 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 95cc19c8cce 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 7800566a28a 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new bdac2f919c2 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 9873c79add7 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 85acb4c8562 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 9afc8619b27 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new b548c66124d 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 76a16211b94 139: onsuccess: #599: 1: Success after binutils: 10 commits new 6441d3e55da 140: onsuccess: #600: 1: Success after gcc: 23 commits new ea6cd74f4dd 141: onsuccess: #601: 1: Success after linux: 794 commits new 4d1a01a4071 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 7c6599d840e 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new de5b8a82ba6 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new d21ab754805 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 2f9620697ec 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 322d4fed547 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new cb2bc6c39b2 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new ad8409d436a 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 7b9a528a713 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 05646a5c7d6 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new ffb1e254d1e 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new cc81ed86589 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new e052323ab50 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new d9dacf0100e 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 423d152dffb 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new d29b43be1d7 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new f820cefe1c3 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 94a99765540 159: onsuccess: #620: 1: Success after binutils: 12 commits new 8a7171ed535 160: onsuccess: #621: 1: Success after gcc: 11 commits new 46099ba55ff 161: onsuccess: #623: 1: Success after glibc: 9 commits new 6a17c4ff396 162: onsuccess: #624: 1: Success after linux: 10 commits new ebd2e2f4d4c 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 0f06d5dd167 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 45a9048a3f0 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 94534de5a42 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 0cba5c84bae 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 0ca65c020b2 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 2ba9d6fa81c 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 2ae0f2ec205 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new e93315cb775 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 298db8c1178 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 09423a865e0 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new a28dddd5601 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 78c5339f345 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 7272430cc4f 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 4d66d1a8998 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 70778682171 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 4f4d28a1b4b 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 4bc27f92496 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new e611daa85d6 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 4932369b070 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new fb9ae3d6521 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 51e0862fe1e 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new d0196ddc0a3 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 994735cef55 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 0575139bf9a 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 09cce729a9d 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 4e04ba7374f 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 2ce7e4b6a12 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 2320c935f0f 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 2ae60a302f4 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 0579e4cb3cb 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new bcb214c7fc6 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 002499e8a73 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 95cc3d5467b 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new d57954f36d8 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 9ed6b71f6a7 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 58510e71a93 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new c53cd082335 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 5744de6eb0d 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 1faf9fa6a7c 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 8eb6e26d2c6 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 64bc9c03f7e 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 72316afad0c 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new d3502d04631 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 98896b558eb 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 810ffc5750b 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new f40bffcd5f0 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 437259df509 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 4b2748380bc 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 78b1b158406 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 5947675283c 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new bca0dc38aec 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 0863b5ffcf6 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 9b1192b49ba 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new ac359510777 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new da6c97b79a5 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 41be65ac343 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new e17e44ed193 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 1974fcea928 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 153a17eb179 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 321b1cc07fe 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new db1cec72008 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 14131ed17cc 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new 6a136c9d06b 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new b75e37b546b 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 86ccc7dfc63 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] new 29313e56bfc 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new b8f017a8a41 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 45eff6ba742 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 283ab35d399 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new d1cc93aa0b1 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gc [...]

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 (51a972b909e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]

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 2032 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2492 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 49508 -> 49268 bytes 04-build_abe-gcc/console.log.xz | Bin 235476 -> 236868 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9096 -> 8780 bytes 07-build_abe-glibc/console.log.xz | Bin 232456 -> 232448 bytes 08-build_abe-gdb/console.log.xz | Bin 47112 -> 46708 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3820 bytes 10-build_abe-check_gcc/console.log.xz | Bin 11160 -> 9612 bytes 11-check_regression/console.log.xz | Bin 4608 -> 5836 bytes 11-check_regression/mail-body.txt | 35 - 11-check_regression/mail-subject.txt | 1 - 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 77 +- 12-update_baseline/console.log | 68 +- 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/changes-list-long.txt | 32 + mail/changes-list-short.txt | 1 + mail/mail-body.txt | 35 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 38 +- sumfiles/g++.log.sep.xz | Bin 86148 -> 71732 bytes sumfiles/g++.log.xz | Bin 2889652 -> 2878556 bytes sumfiles/g++.sum | 34 +- sumfiles/g++.sum.sep | 7187 ++++++++++++++++++++++----------- sumfiles/gcc.log.sep.xz | Bin 87928 -> 68272 bytes sumfiles/gcc.log.xz | Bin 2518088 -> 2459744 bytes sumfiles/gcc.sum | 20 +- sumfiles/gcc.sum.sep | 6635 +++++------------------------- sumfiles/gfortran.log.sep.xz | Bin 17384 -> 30176 bytes sumfiles/gfortran.log.xz | Bin 959236 -> 958048 bytes sumfiles/gfortran.sum | 5 +- sumfiles/gfortran.sum.sep | 2526 +++++++----- sumfiles/libatomic.log.xz | Bin 2284 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233880 -> 233784 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 6140 -> 17112 bytes sumfiles/libstdc++.log.xz | Bin 481288 -> 468272 bytes sumfiles/libstdc++.sum.sep | 292 +- 49 files changed, 7775 insertions(+), 9257 deletions(-) delete mode 100644 11-check_regression/mail-body.txt delete mode 100644 11-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt