Hi Andrea, Am 14.08.19 um 16:51 schrieb Andrea Pescetti: > Matthias Seidel wrote: >> We already have the build id, the build >> date and now the git hash (which is a unique link to the last commit it >> was based on) >> This is how we did it with SVN, why should we change it? > > Because we are dropping information. The SVN revisions are always > increasing, and thus (independent on the build date, which can be at > any moment) I can compare two builds and retain information on which > came first. > > With git of course this doesn't hold, i.e., you cannot say which > commit came earlier between abcd1234 and 5678abcd. So I see some added > value if we enrich it this way.
OK, then we could do it like Peter suggested and add the (commit) date after the Git hash. Something like this (in case of my build): AOO420m2(Build:9821) - Rev. 20ef23374c - Mon Aug 12 21:11:24 2019 +0200 2019-08-13 15:58 - CYGWIN_NT-10.0 x86_64 - Development Test Build Matthias > > Regards, > Andrea. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org >
smime.p7s
Description: S/MIME Cryptographic Signature
