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

Re: Commit signing

From
Nicolas Pitre <nico@cam.org>
Date
Jan 15, 2007, 16:47 UTC
Message-ID
<Pine.LNX.4.64.0701151143470.2577@xanadu.home>
In-Reply-To
<200701151301.l0FD1vPg007623@laptop13.inf.utfsm.cl>
On Mon, 15 Jan 2007, Horst H. von Brand wrote:
Show 14 quoted lines
> Andy Parkins <andyparkins@gmail.com> wrote:
> 
> > Again true.  What has that to do with Git though?  Why shouldn't Git have 
> > features that let people with different methods of development from you use 
> > it?
> 
> As long as nobody else ends up paying the cost...
> 
> >     It is certainly true that signed commits /is/ a feature.  And it's a 
> > feature that some people might want.  If there isn't a technical argument 
> > against it, what does it matter?
> 
> It needs to be accomodated in the commit object format, so it means
> an(other) incompatible change there.

Not really. Nothing prevents from having a signature block at the bottom of the commit message, just like signed tags.

> Need to add checking for properly
> signed commits all the way when slurping in a stream of changes. Need to
> set the whole up so it can bail out as if nothing ever happened in case one
> commit doesn't check out (this is probably easy).

... and if you don't care about the signature you may ignore it entirely.

Nicolas
Previous: Johannes Schindelin
Message 3 of 3 in “Re: Commit signing”
  1. Horst H. von BrandJan 15, 2007
  2. Johannes SchindelinJan 15, 2007
  3. Nicolas PitreJan 15, 2007

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.