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

Re: [PATCH 1/2] Documentation/technical: signature formats

From
Jakub Narębski <jnareb@gmail.com>
Date
Oct 25, 2014, 08:30 UTC
Message-ID
<544B5FA1.2050804@gmail.com>
In-Reply-To
<xmqq7fzshqrb.fsf@gitster.dls.corp.google.com>
W dniu 2014-10-22 21:02, Junio C Hamano pisze:
Show 7 quoted lines
> A mergetag is not fundamentally a "signature" in the above sense,
> though.  It is just a dump of the object content in a regular object
> header field (hence indented by one SP), and its contents having PGP
> SIGNATURE is merely a natural consequence of the object recorded
> being a signed tag.  So the description of it in the same place as
> description for signed tags and signed commits feels a little bit
> out of place, but I do not think of a better place to describe it.

Does this mean that you can merge annotated (but not signed) tag, and have it (as description of merged branch) in 'mergetag' header?

-- 
Jakub Narębski
Previous: Junio C HamanoNext: Michael J Gruber
Message 7 of 9 in “document signature formats”
  1. 0/2 document signature formatsMichael J Gruber, Oct 22, 2014
  2. 1/2 Documentation/technical: signature formatsMichael J Gruber, Oct 22, 2014
  3. Jakub NarębskiOct 22, 2014
  4. Junio C HamanoOct 22, 2014
  5. Michael J GruberOct 24, 2014
  6. Junio C HamanoOct 24, 2014
  7. Jakub NarębskiOct 25, 2014
  8. Michael J GruberOct 30, 2014
  9. 2/2 Documentation/technical: document push certificate formatMichael J Gruber, Oct 22, 2014

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.