git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Philipp Marek" <philipp@marek.priv.at>
To: git@vger.kernel.org
Subject: [RFC] Support for arbitrary tags in commits
Date: Tue, 11 Jan 2011 13:23:32 +0100 (CET)	[thread overview]
Message-ID: <74b0628dffbd2bc0adabe5e8b0a10960.squirrel@webmail.hitco.org> (raw)

Hello everybody,

I'd like to attach some additional data to commits.

The best way I've found (so far) is to put an additional header line in the
commit header that references an additional blob.


Currently I've found "tree", "parent", "author", "committer", and so on; git
accepts additional lines before the "\n\n" separator (and the commit message),
so that's where I'd like to put the line.

"git fsck" allows that, too; only "rebase -i" and similar don't know about them
(yet), and discard them.


Now I want to ask:
 * Is this acceptable?
 * If yes, I'd try to provide a patch to make "amend" and similar keep the
   header-lines (by collecting them in order - obviously with editing commits
   a header could exist multiple times).
 * Perhaps there should be an option for "git-commit" that inserts arbitrary
   header lines?
 * Is there some documentation for the commit-file format so that this can be
   written down?
 * How should namespace-issues be handled?
   I can imagine that multiple people want to put data there, how should the
   tag be allocated?
   This could be solved by the previous point, ie. there's some page that
   header tags should be registered at to avoid collisions.


Thank you for all feedback.


Regards,

Phil


-- 
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

             reply	other threads:[~2011-01-11 12:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 12:23 Philipp Marek [this message]
2011-01-11 12:40 ` [RFC] Support for arbitrary tags in commits Thomas Rast
2011-01-11 13:48   ` Philipp Marek
2011-01-11 13:53     ` Thomas Rast

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=74b0628dffbd2bc0adabe5e8b0a10960.squirrel@webmail.hitco.org \
    --to=philipp@marek.priv.at \
    --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).