| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Git revision in tarballs |
| Date: | 2021-07-15 08:33:11 |
| Message-ID: | CABUevEx=nMVABr9cZrqkaPjFLjZm_pRosUrdh90_VwzWCWdTJw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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).
What do people think of the attached?
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
| Attachment | Content-Type | Size |
|---|---|---|
| gitrevision.patch | text/x-patch | 472 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gilles Darold | 2021-07-15 08:59:07 | Re: [PATCH] Hooks at XactCommand level |
| Previous Message | Dean Rasheed | 2021-07-15 08:10:19 | Re: Enhanced error message to include hint messages for redundant options error |