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

Re: RFC: update hook for GPG signed submission on secured branches

From
John Keeping <john@keeping.me.uk>
Date
Jan 16, 2015, 19:59 UTC
Message-ID
<20150116195950.GK26383@serenity.lan>
In-Reply-To
<BD3DE7B299FE458287DC8C829CEADEC2@black>
On Fri, Jan 16, 2015 at 02:47:25PM -0500, Jason Pyeron wrote:
Show 7 quoted lines
> > I am not sure if the design of this, to require signature only on
> > the tip commit, is sound.  That is not a -bug- in the script,
> > though.
> 
> It is to handle the "all my devs worked on this, they do ________
> GPG", so as long as the tip os signed, it is an implicit I am
> responsible for what is submitted.

Isn't this an ideal scenario for using the signed pushes introduced in Git 2.2.0?

Previous: Jason PyeronNext: Junio C Hamano
Message 5 of 6 in “RFC: update hook for GPG signed submission on secured branches”
  1. Jason PyeronJan 16, 2015
  2. Junio C HamanoJan 16, 2015
  3. Junio C HamanoJan 16, 2015
  4. Jason PyeronJan 16, 2015
  5. John KeepingJan 16, 2015
  6. Junio C HamanoJan 16, 2015

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.