43476 2022-08-09 04:22:12 +0300 FR: Add SHA1 to "build x from y fetched at z" line 2022-08-27 21:12:07 +0300 1 1 2 Infrastructure Infrastructure girar unspecified x86 Linux NEW P5 normal --- 1 vt placeholder glebfm ldv cas oldest_to_newest 213542 0 vt 2022-08-09 04:22:12 +0300 In the Girar emails, line #300 build 1.13-alt1 from /people/vt/packages/libdeflate.git fetched at 2022-Aug-08 22:23:23 It would be better if it shows SHA1 commit rather than (or additionally to) TAG and DATE. Because, it's possible to `git diff` locally commit SHA1 with HEAD, but it's not possible to diff TAG (because it's frequently overwritten) or DATE. It's useful sometimes to see what is changed between builds, but tags are transient because we need to overwrite them to trigger a build and dates aren't resolve to anything. 213543 1 ldv 2022-08-09 09:24:56 +0300 Wouldn't the line become unreadably long? 213546 2 vt 2022-08-09 10:15:42 +0300 It also will start to have what to read. 213547 3 vt 2022-08-09 10:17:58 +0300 Also, date (such as "at 2022-Aug-08 22:23:23") can be replaced completely with a "short sha1". 213548 4 vt 2022-08-09 10:23:26 +0300 Also2, mutt is able to wrap long lines, and Incominger web view is usually much wider on the screen and have room to extend the line. And finally this info is so useful and if it does not fit one line a second line could be added. 214110 5 vt 2022-08-27 21:12:07 +0300 Почему с логе не находится места для полезной информации?