fun with git log

[Elliott Mitchell]

On Sat, Nov 30, 2024 at 04:34:58PM +0100, Bjørn Mork via openwrt-devel wrote:
> 
> Looking at include/download.mk I found that the timestamp is taken from
> a TAR_TIMESTAMP variable, with rules to set that to a stable and
> reasonable value for different version control systems.  But there were
> no relevant changes to any of that code since the last time I built
> this.  The git rule was
> 
>  export TAR_TIMESTAMP=`cd $(SUBDIR) && git log -1 --format='@%ct'`
> 
> which looked fine to me.  But just to be sure, I tested it in my openwrt
> source tree.  And that's a "Doh!" moment:
> 
> bjorn at canardo:/usr/local/src/openwrt$ git log -1 --format='@%ct'
> gpg: Signature made Sat Nov 30 14:24:36 2024 CET
> gpg:                using EDDSA key 687BE08049F161EDA67AB21222044ECBBFA4615D
> gpg: please do a --check-trustdb
> gpg: Good signature from "Bjørn Mork <bmork at telenor.net>" [ultimate]
> gpg:                 aka "Bjørn Mork <bjorn at mork.no>" [ultimate]
> Primary key fingerprint: F461 6F51 2B11 3B3C 1827  3C21 E197 FC12 EFF0 5ECD
>      Subkey fingerprint: 687B E080 49F1 61ED A67A  B212 2204 4ECB BFA4 615D
> @1732973075
> 
> 
> So, what happened here?  I can tell you: I recently set
> 
>  log.showSignature = true
> 
> in my global git config.  The special problem with the package source
> was the top commit was signed.

Reads like a conventional, not-quite-the-right format.  I suspect
substituting "--format='format:@%ct'" /may/ solve the problem.
Otherwise simply figuring out the right way to ensure it outputs what is
wanted and nothing else.


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         ehem+sigmsg at m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445