Re: Extra metadata in the commit?
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Apr 24, 2009, 23:55 UTC
- Message-ID
- <alpine.DEB.1.00.0904250154080.10279@pacific.mpi-cbg.de>
- In-Reply-To
- <d411cc4a0904241547p64c0af2bycae20cd4b26e43f6@mail.gmail.com>
Hi,
On Fri, 24 Apr 2009, Scott Chacon wrote:
Show 9 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.
I'd suggest keeping it in the commit body, for better visibility and easier handling by tools.
Ciao, Dscho