Re: extra headers in commit objects

From: Shawn O. Pearce <spearce@spearce.org>
Date: Feb 3, 2010, 20:31 UTC
Message-ID: <20100203203148.GF14799@spearce.org>
In-Reply-To: <9b18b3111002031143h63aaa6bpa4c91d140a769bb0@mail.gmail.com>

demerphq <demerphq@gmail.com> wrote:

Show 8 quoted lines

> On 3 February 2010 20:26, Petr Baudis <pasky@suse.cz> wrote:
> Right. The only solution i can see would have had to have been
> implemented already. And that would involved some headers being marked
> "pass through", some "marked throw away on cherry-pick" and some
> "choke horribly if you find this and dont know what it is".
> 
> And even with somethng like that one wonders if  notes arent really a
> better alternative to user defined headers anyway?

Yes, exactly.

I think notes turn out to be a much better way to store this extra data, provided you are OK with them being disconnected during an amend, cherry-pick, filter-branch, or rebase... :-)

And unlike additional headers, git implementations will likely
support notes, because they are a good way to attach additional
user data onto commits.

-- 
Shawn.