From: Scott Chacon <schacon@gmail.com>
To: git list <git@vger.kernel.org>
Subject: Extra metadata in the commit?
Date: Fri, 24 Apr 2009 15:47:55 -0700 [thread overview]
Message-ID: <d411cc4a0904241547p64c0af2bycae20cd4b26e43f6@mail.gmail.com> (raw)
Hey all,
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?
Thanks,
Scott
next reply other threads:[~2009-04-24 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 22:47 Scott Chacon [this message]
2009-04-24 23:06 ` Extra metadata in the commit? Junio C Hamano
2009-04-24 23:55 ` Johannes Schindelin
2009-04-25 9:49 ` Alex Riesen
2009-04-25 12:08 ` Johan Herland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d411cc4a0904241547p64c0af2bycae20cd4b26e43f6@mail.gmail.com \
--to=schacon@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).