Re: Git revision in tarballs - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Git revision in tarballs
Date
Msg-id d19e0ae2-33d6-85d8-df59-29ed4b92f34a@enterprisedb.com
Whole thread Raw
In response to Git revision in tarballs  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Git revision in tarballs  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
On 15.07.21 10:33, Magnus Hagander wrote:
> I think it'd be useful to be able to identify exactly which git commit
> was used to produce a tarball. This would be especially useful when
> downloading snapshot tarballs where that's not entirely clear, but can
> also be used to verify that the release tarballs matches what's
> expected (in the extremely rare case that a tarball is rewrapped for
> example).

Or we could do what git-archive does:

     Additionally the commit ID is stored in a global extended
     pax header if the tar format is used; it can be extracted using git
     get-tar-commit-id. In ZIP files it is stored as
     a file comment.



pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: [POC] verifying UTF-8 using SIMD instructions
Next
From: Daniel Gustafsson
Date:
Subject: Re: Git revision in tarballs