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

Re: New Proposal (simple) for Metadata in Git Commits: git-meta

From
Shawn O. Pearce <spearce@spearce.org>
Date
Dec 16, 2009, 16:30 UTC
Message-ID
<20091216163036.GE18319@spearce.org>
In-Reply-To
<7349A827-41D5-434F-85FE-D49980A7D501@lenary.co.uk>
Sam Elliott <sam@lenary.co.uk> wrote:
Show 12 quoted lines
> On 15 Dec 2009, at 23:05, Shawn O. Pearce wrote:
>> If you dropped the --git-meta-- tags above, JGit would happily
>> recognize the awesome: and Github: tags, but it might need a bit
>> more work to recognize the nested user: tag.  Also, you'd be able
>> to use git-meta on the git and Linux kernel repositories to pull
>> out and work with Signed-off-by, Acked-by, etc.
>
> I'm not entirely sure about this approach. The current implementation  
> also works with PGP-signed tags, where the information is not  
> necessarily going to be at the bottom of the message when i use `git- 
> cat-file -p`. I think it shouldn't be too hard to also have git-meta  
> read any YAML-like data just before the signing message.

Ah, good point. But as you point out, it should be simple enough to detect a PGP signature on the bottom and just clip that off the end, and then perform the YAML-like data parsing on the footer.

-- 
Shawn.
Previous: Shawn O. PearceNext: Johan Herland
Message 3 of 4 in “New Proposal (simple) for Metadata in Git Commits: git-meta”
  1. Sam ElliottDec 15, 2009
  2. Shawn O. PearceDec 15, 2009
  3. Shawn O. PearceDec 16, 2009
  4. Johan HerlandDec 17, 2009

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.