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-aarch64 in repository toolchain/ci/base-artifacts.

discards e83d8d5d224 222: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 795d77fac22 221: onsuccess: #27: 1: Success after binutils/gcc/linux/gl [...] discards 9681a8a10fc 220: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 7d36c84e7d6 219: onsuccess: #24: 1: Success after binutils/gcc/linux/gd [...] discards 57c668edb19 218: onsuccess: #23: 1: Success after binutils/gcc/linux/gd [...] discards 68bf74755d4 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] discards d056f5a7610 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] discards fa0433690a8 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards b86fcbde0a5 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards a2d20fba23d 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 7ef167f0a11 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 84b14396479 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 31c91f687fc 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards ad5a2f96ea6 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 93780a4be24 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards ac5666ca48c 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards e2db64ed2f7 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 08095b09123 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 62fdb5f8fb0 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 0745c95bf35 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards dba71bbf060 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards dbc89bba9c0 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards c6df0592992 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 7277527806c 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards bcdbc85ddb9 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 45463bab064 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards c1051100b53 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 1a81ec16840 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 6f8bc38f001 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards c7b1a472569 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 76226bbd11e 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 6bd4987d0e7 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 35fac8a7e22 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 7b32ff1c80c 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards 79e671daaa1 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 6b8fceec930 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 307fb877f21 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards f6edc993ddd 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards a9b3f4ca26b 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards e654f49933b 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards a03b3a52c5f 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards 95e08c4f2c6 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards 6058de5abbc 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 4ae1c9f0f86 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards 9fad30e021d 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 4596098c0a2 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards e57834e8f9d 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 6ab183c4025 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards b5044497f75 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards 7b1d41e2f4b 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards dc0afe3cf00 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards bf1ee58beb3 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 66446bc25d0 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards 7a626130a0d 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 5bcc183944b 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 310915783e0 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards ca60ff0c447 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards b83edb9dda7 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards ab2a49e4841 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards 6e580635d9c 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 3e4412c3f69 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 6b854a2900d 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards c5ccc00bb5e 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards a6703e227b0 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards bf6bdb21ac9 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards 86fd00b8f11 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards 3ac0c91496f 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards ecb06a3728c 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards e81ef9eb2b3 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards dc069503a7f 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards bfde80aa5a8 152: onsuccess: #903: 1: Success after linux: 22 commits discards b47c9560a40 151: onsuccess: #902: 1: Success after glibc: 8 commits discards c8fb16f88cf 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 31c5475c0c0 149: onsuccess: #899: 1: Success after binutils: 15 commits discards bc5f3338e92 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards 2ad22ffecd1 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards 9b408c5373b 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards 345662cf19b 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 9d89c1e3849 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards fd637f316ff 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards 34bb472705f 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards b7a34f3e051 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards f7f238a844e 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 50339e1138d 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 5d1aa726157 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards e5d67bc6878 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 22bd1a9cf7d 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards c0253b4c547 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 355389863f1 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards 6919234bc94 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards ba425f76099 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 177ddfe5b50 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards 5c6f49e167e 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards 7302dd52ff1 129: onsuccess: #878: 1: Success after linux: 3008 commits discards db5f4b58ceb 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 71efa1015a2 127: onsuccess: #874: 1: Success after linux: 219 commits discards e75e4201e19 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 16d37c71839 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 958128ce0a4 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards a9140ec1fe3 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 2af34da1d04 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new a7cac6d2e92 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new e64b494251c 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 4d551cd3f86 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new c955a8d9a93 125: onsuccess: #871: 1: Success after binutils: 26 commits new 7ae7b4452bc 126: onsuccess: #873: 1: Success after glibc: 2 commits new 9afc5bb187d 127: onsuccess: #874: 1: Success after linux: 219 commits new e8e952c6ab2 128: onsuccess: #876: 1: Success after binutils: 12 commits new f7a5f652397 129: onsuccess: #878: 1: Success after linux: 3008 commits new d12d1e90d69 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 25ce3949173 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new 467ee4225bc 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 21b93c36ee3 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new f4f75aa07d7 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new abcf2814f23 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 3b52f40e6d4 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new e93a3de87bc 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 8495b37b9a8 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 61b4dccd369 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 0ff34c7c2b2 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 9532ae9f776 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new adb97dac0dd 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new c6c08579a70 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new cc9d9a0f7eb 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new 9c745a463c7 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new f50be1b6ef8 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new da65aae5bae 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new 1ec37a078fd 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new 3d8df75177c 149: onsuccess: #899: 1: Success after binutils: 15 commits new 24462e59bae 150: onsuccess: #900: 1: Success after gcc: 11 commits new f347dca3d37 151: onsuccess: #902: 1: Success after glibc: 8 commits new c95265ec7f3 152: onsuccess: #903: 1: Success after linux: 22 commits new 6398a01d140 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 96e5dfb293f 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new 3c5798f4c5a 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new a90f8a95058 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new cde8d237416 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new 3d944c79d8a 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new 62916e98783 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 0884f61d49c 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new a7139fc26b9 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new a6202c03682 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 94e699d48ae 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 26b0f662ed4 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new f0a9e0504d2 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new ebce4b5b4c9 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 47721cbc1b0 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new ae073edfc38 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 1369c4bcdb5 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 8d28a6a88ec 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new 0d77b3b8406 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 58eeb21332b 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new c3dde12a55c 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new 3de9e49faf3 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new cf76e861a1d 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 1c4cdfa58c1 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 0c184e11458 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 5ed5bb60825 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 5fef94ad2cf 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new 992ec2ed1ba 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 356d9dc70fb 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new 8aa03d67601 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new e34cd11810a 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new 698f9bc7106 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new de43f546559 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new c4b3e0edefa 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new fe8f6ba1b65 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 151c924d208 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 11d58e7e21a 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new f6d78c02377 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 584ce986496 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 1f308232458 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new a1ac618a53e 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new a36f142d5d1 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 553f0e111c4 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new c55f28ef6f5 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new da25aa609a7 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 0d9afc7ab83 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 92783db3869 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 7ced618af1f 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new faaccf555a7 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 0ee4da442a2 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new a8f7ba540b2 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 111d98b02b9 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 3a4325bde88 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 2ca30455a32 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 2337823fce3 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new f594b1dee93 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 1939b3f050f 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new fc388ac6685 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new d29259f4edc 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 7f5fb54f59e 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new f95d3013c96 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 5ccff2b38e4 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 5d16290cff3 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new b0ae333d7ad 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] new 8ed54f4b6c3 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] new c75b73dd4d0 218: onsuccess: #23: 1: Success after binutils/gcc/linux/gd [...] new d41ac80ecb9 219: onsuccess: #24: 1: Success after binutils/gcc/linux/gd [...] new c8a0ec27f20 220: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new f388f5b9aea 221: onsuccess: #27: 1: Success after binutils/gcc/linux/gl [...] new 441bf372a75 222: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new d2e4b0b410d 223: onsuccess: #29: 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 (e83d8d5d224) \ 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 2044 -> 2120 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 35676 -> 35104 bytes 04-build_abe-gcc/console.log.xz | Bin 203048 -> 205456 bytes 06-build_abe-linux/console.log.xz | Bin 8392 -> 8952 bytes 07-build_abe-glibc/console.log.xz | Bin 241660 -> 242832 bytes 08-build_abe-gdb/console.log.xz | Bin 35108 -> 35116 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3796 bytes 10-build_abe-check_gcc/console.log.xz | Bin 10404 -> 10548 bytes 11-check_regression/console.log.xz | Bin 5952 -> 10756 bytes 11-check_regression/jira-body.txt | 1 - 11-check_regression/mail-body.txt | 2 +- 11-check_regression/results.compare2 | 1955 +++++- 12-update_baseline/console.log | 36 +- 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 75480 -> 66112 bytes sumfiles/g++.log.xz | Bin 3704980 -> 3693960 bytes sumfiles/g++.sum | 1555 +++-- sumfiles/g++.sum.sep | 11265 +++++++++++++++----------------- sumfiles/gcc.log.sep.xz | Bin 66896 -> 63060 bytes sumfiles/gcc.log.xz | Bin 3214836 -> 3214604 bytes sumfiles/gcc.sum | 398 +- sumfiles/gcc.sum.sep | 7551 +++++++++------------ sumfiles/gfortran.log.sep.xz | Bin 26716 -> 24744 bytes sumfiles/gfortran.log.xz | Bin 1081204 -> 1083172 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 2951 ++++----- sumfiles/libatomic.log.xz | Bin 2296 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 235656 -> 235668 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 6780 -> 19232 bytes sumfiles/libstdc++.log.xz | Bin 448460 -> 450948 bytes sumfiles/libstdc++.sum.sep | 35 +- 44 files changed, 12660 insertions(+), 13146 deletions(-) delete mode 100644 11-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt