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.