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

Re: Extra metadata in the commit?

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 24, 2009, 23:06 UTC
Message-ID
<7vws998xdf.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<d411cc4a0904241547p64c0af2bycae20cd4b26e43f6@mail.gmail.com>
Scott Chacon <schacon@gmail.com> writes:
Show 11 quoted lines
> I'm working on a hg<->git bidirectional tool using Git as the
> communication protocol, so there is a bunch of Hg metadata that I need
> to keep in Git to ensure I can convert commits created in Hg back into
> the exact same objects after they upload to the Git db and then come
> back down.  This means storing explicit rename info, branch names, etc
> somewhere without messing up Git clients that want to work on the same
> repo.  So, I can keep this data in the commit message, but I thought
> it would be cleaner to keep it as extra fields in the commit object
> before the "\n\n" separator.  Before I go too far down this road, is
> there anything horrible that might happen in any of the core Git tools
> if extra data is there?

Not that I know of but it is highly unlikely that such a patch will be accepted, given the history of discussion around that area.

Previous: Scott ChaconNext: Johannes Schindelin
Message 2 of 5 in “Extra metadata in the commit?”
  1. Scott ChaconApr 24, 2009
  2. Junio C HamanoApr 24, 2009
  3. Johannes SchindelinApr 24, 2009
  4. Alex RiesenApr 25, 2009
  5. Johan HerlandApr 25, 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.