Re: Storing (hidden) per-commit metadata

From: Jeff King <peff@peff.net>
Date: Feb 21, 2010, 06:34 UTC
Message-ID: <20100221063433.GA2840@coredump.intra.peff.net>
In-Reply-To: <32541b131002201057t31fc8a6aydb0942171fe1b8c8@mail.gmail.com>

On Sat, Feb 20, 2010 at 01:57:31PM -0500, Avery Pennarun wrote:

> As for git-notes, they sound like they would be useful for this sort
> of thing.  I haven't tried them yet, but my understanding is that
> notes anywhere other than the "default" notes ref are not shown in
> commit messages, so you can use them for whatever you want.

I would want to hear more about the actual data being stored. The strength of notes is that you can _change_ them after the commit has been created. And the price you pay is that they are more annoying to move around, because they are in a totally different ref.

If this is data that is being generated at the time the commit is created and then set in stone, then it probably should be part of the commit object.

If the only problem is that the data is ugly in "git show", then perhaps we need a "suppress these pseudo-headers" feature for showing logs. It keeps them easily available for inspection or for --grep, but most of the time you would not see them.

-Peff