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 9c1597d9e6d 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards f87ee3c2d75 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] discards e48a64fe758 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards c348bcd096c 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 66d2bbbecac 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards be2ee92923e 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards e79942c5377 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 58876eb0efb 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 1d4fa109769 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 0e04ee8cb78 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards 59572290413 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 7946d2cb643 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards e93d547af62 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 286d3307987 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 4cca520342a 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 45bec1d35fe 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 4aaad9a14cb 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 327d5524db8 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 0380557ee21 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards abacfc6a4ea 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ae85dab48a6 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 0caf893d34a 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 6e5823b5c1f 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 52c35787263 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards f925e27f78b 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 3463ae5841d 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards a6f245a6c25 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards b56b1f1a58b 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards b654152b067 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards b1e43f03c47 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards d6ab3232367 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 3373d2d3969 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 14ebbb39908 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards e49652208d0 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 03948748a97 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards f86eb5e8793 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 2cc4d480aeb 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards b8115337e1f 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 557d15b826c 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 7f2559ac2a7 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards c9da7953de4 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 78807c04eab 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards ba65777eae6 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 588c4a8c72b 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards ac85a8974bc 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards fcd9cb51d64 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards aae70307ab0 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 71a88cd0bf5 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards 2f0168f6ef9 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards f00ff652c04 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards f5b11163316 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 87a5575ee7a 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 8ab3484c058 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 48ff78d8478 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards af074126e72 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards be5b8ff271d 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards b290977c26c 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards c48e50d77c1 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 888d13581f6 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 9c57f0729da 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 35a47537397 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 50fd60d03a7 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 64a57758b4d 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards d0271d6d5f8 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards f65db080f8f 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 7e31d433a88 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 3ae3b0687ae 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 425abda21b2 162: onsuccess: #624: 1: Success after linux: 10 commits discards b832dd99d80 161: onsuccess: #623: 1: Success after glibc: 9 commits discards e173f91de0d 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 50fcf233b0c 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 3c0ad7d2805 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards e223015a672 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 148d840f502 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards dbe625a62ff 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 307b0fcccaa 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards 14a77e975a4 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards 829b7a75a39 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards eac171ea4f0 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 33c1fb06f7a 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards ea1f9215488 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 05ab5f875d7 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 401ff94ab05 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 15ecc97e8fc 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 0178a129764 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards afe6f7f0375 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 6ae39aea05f 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 4ef0f317cb4 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards b7961e51cf9 141: onsuccess: #601: 1: Success after linux: 794 commits discards 8a7afc2fc74 140: onsuccess: #600: 1: Success after gcc: 23 commits discards affab5c5011 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 89d16d72651 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards d969226b849 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 7bbfe2d5df7 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 9ba91237d2a 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards ff11815c8a6 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards cb54ec526d7 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards edea18e5a43 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 730871843a0 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 06186164915 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 0d1c82f4d90 129: onsuccess: #588: 1: Success after linux: 4 commits new ddce5c47990 129: onsuccess: #588: 1: Success after linux: 4 commits new 1e18927a462 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 92a74456dc2 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new ca6cf9c519e 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 84dd60f5109 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new cd6bac438b9 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 9c75560e162 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 82e98e3d340 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new c8ebdf51d19 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 9d429ce7565 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 432c0e4cfe3 139: onsuccess: #599: 1: Success after binutils: 10 commits new 4dafde96d4b 140: onsuccess: #600: 1: Success after gcc: 23 commits new fedefb324c0 141: onsuccess: #601: 1: Success after linux: 794 commits new 9b1a69a881b 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 4c144c91dc8 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 0dbe369448a 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new a4d12048f6d 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 546386c9793 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new f01866a975d 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 61d06b064e7 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 4eea8ac3388 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 7840803ddb9 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 95f9c57e407 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 118d6e89967 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new c3726fd77c7 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 50bd316c51f 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new 57378156493 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 8fb7a9ca5d8 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new d8f587af580 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 80fd45b1947 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new c39e319f1c2 159: onsuccess: #620: 1: Success after binutils: 12 commits new 32f185d9c1f 160: onsuccess: #621: 1: Success after gcc: 11 commits new 0dca71117e1 161: onsuccess: #623: 1: Success after glibc: 9 commits new 67a0fff23d7 162: onsuccess: #624: 1: Success after linux: 10 commits new c426fb8df3a 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 0b333cfab8e 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 1a5bfe5c6d9 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new fb7b44588fe 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new e17efe0d09e 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 98d86ecdc1f 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 8d76214155d 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new ce44355f856 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 018afb09fec 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 337510b50dd 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 5353666c86c 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new bb3d63af66d 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 9cfca273bfd 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 937c96840e4 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 046406c1630 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 391adfb4a36 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new e240a28d4bd 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 808ad48ad81 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 4375338b943 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 03eeb318693 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 4ccefb689b0 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 04bca5efb38 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 820c72f3b0b 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 83dec5ec7f2 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 23dc5c75daa 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 8328fc5b4c8 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new bd58720d63b 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new ea6500f738c 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new baddeef55e3 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 5eacc0feff2 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 14c62fb0e77 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 0247e36c3a9 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 48f632c64d8 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 658774bb0a3 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 681fa0d4adb 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 04a80b6feb1 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 03db5fc1de9 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new edb497ce2d9 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new a6db7ac5559 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 5ea1b649b1b 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 33a363eebf2 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 3a195f0439f 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 5efec1478e7 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 8e73e722fab 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new f1e3e790c3c 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new dcb1cff0286 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new f8134f8904a 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 24365d5c281 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 777c0bcaab8 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 5f4fb11dd88 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 14a45f6097d 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 4f82be7f064 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new b07ec9c4ef6 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 5a1c5d97400 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 720d2c51885 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 9b12767ce62 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new c73309c9372 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 3cf0dc7582f 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new f36b3751c90 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 13e7058a3a9 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new ae6f3729748 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new cf7f1eb4a02 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new d5834b95a86 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new a525d5d4045 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new 56bcb2678dc 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 9f5c9c3c793 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] new 9e5b542a1a4 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new de5703d5064 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...]
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 (9c1597d9e6d) \ 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 2028 -> 2236 bytes 02-prepare_abe/console.log.xz | Bin 2564 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 49012 -> 49052 bytes 04-build_abe-gcc/console.log.xz | Bin 236856 -> 238088 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8396 -> 8424 bytes 07-build_abe-glibc/console.log.xz | Bin 232940 -> 232588 bytes 08-build_abe-gdb/console.log.xz | Bin 47500 -> 47260 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3772 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9116 -> 9644 bytes 11-check_regression/console.log.xz | Bin 5716 -> 9976 bytes 11-check_regression/jira-body.txt | 1 - 11-check_regression/mail-body.txt | 2 +- 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 1699 ++++- 12-update_baseline/console.log | 62 +- 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 | 1 - mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.sep.xz | Bin 81208 -> 76972 bytes sumfiles/g++.log.xz | Bin 2912268 -> 2911672 bytes sumfiles/g++.sum | 1286 ++-- sumfiles/g++.sum.sep | 10725 ++++++++++++-------------------- sumfiles/gcc.log.sep.xz | Bin 67068 -> 63696 bytes sumfiles/gcc.log.xz | Bin 2469108 -> 2484576 bytes sumfiles/gcc.sum | 327 +- sumfiles/gcc.sum.sep | 505 +- sumfiles/gfortran.log.sep.xz | Bin 36364 -> 29272 bytes sumfiles/gfortran.log.xz | Bin 949244 -> 953296 bytes sumfiles/gfortran.sum | 9 +- sumfiles/gfortran.sum.sep | 3723 ++++++----- sumfiles/libatomic.log.xz | Bin 2280 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233936 -> 233812 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 10152 -> 9900 bytes sumfiles/libstdc++.log.xz | Bin 469128 -> 469836 bytes sumfiles/libstdc++.sum.sep | 493 +- 46 files changed, 8876 insertions(+), 10027 deletions(-) delete mode 100644 11-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt