git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Tracability in git commits

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
May 1, 2008, 22:21 UTC
Message-ID
<46a038f90805011521s1d7f5d42k2e9186e5fd4c43b3@mail.gmail.com>
In-Reply-To
<7v63txzw18.fsf@gitster.siamese.dyndns.org>
On Fri, May 2, 2008 at 7:03 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 6 quoted lines
>  I suspect that, with the "push to incoming, vet there and move to
>  verified" workflow, you do not need a special GPG-signed list.  You can
>  instead have the pusher sign the tip using the usual signed-tag mechanism,
>  which would sign the whole history leading to it, and have him push that
>  tag to the incoming together with the tip update.  You obviously do not
>  need nor want to move that signed tag to the final area.

Yes. Though it makes a post-facto audit of who-pushed-which-commits trickier - you'll have to correlate the reflogs in the server with the signed tags. Having an explicit signature on a list of commits is a bit more direct, easier to audit... IMHO anyway ;-)

cheers,
m
-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
Previous: Junio C Hamano
Message 15 of 15 in “Tracability in git commits”
  1. Richard PurdieApr 29, 2008
  2. Johannes SchindelinApr 29, 2008
  3. Junio C HamanoApr 29, 2008
  4. Richard PurdieApr 29, 2008
  5. Shawn O. PearceApr 30, 2008
  6. Ping YinApr 30, 2008
  7. Miklos VajnaApr 30, 2008
  8. Shawn O. PearceMay 1, 2008
  9. Ping YinMay 1, 2008
  10. Jakub NarebskiApr 30, 2008
  11. Richard PurdieApr 30, 2008
  12. Martin LanghoffMay 1, 2008
  13. Martin LanghoffMay 1, 2008
  14. Junio C HamanoMay 1, 2008
  15. Martin LanghoffMay 1, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.