Re: Storing additional information in commit headers

From: martin f krafft <madduck@madduck.net>
Date: Aug 1, 2011, 20:55 UTC
Message-ID: <20110801205523.GB15401@fishbowl.rw.madduck.net>
In-Reply-To: <20110801200149.GA20861@toss>

also sprach Clemens Buchacher <drizzd@aon.at> [2011.08.01.2201 +0200]:

> Notes are tracked using a 'branch' too. It's just a branch in the
> refs/notes namespace, the notes ref. You could simply tag your
> notes ref or point a ref from the refs/heads namespace to it each
> time you create new notes.

Hi Clemens, thanks for responding!

You suggest integrating refs/notes/foo into refs/heads by means of a pointer… at which point we are polluting the branch history space again (think gitk), no?

I appreciate the simplicity of this idea of yours, which I had not thought of. Indeed, maintaining a head at the top of refs/notes/topgit-metadata (or whatever) has charm. I do not mean to discard it at all right now, and will think about this more!

git-notes was designed to be used for such cases, I was pleased to note the configurability. Maybe it is the ticket.

Still: why not commit headers?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
... with a plastic cup filled with a liquid that was almost,
but not quite, entirely unlike tea.
            -- douglas adams, "the hitchhiker's guide to the galaxy"
 
spamtraps: madduck.bogus@madduck.net