Re: [REVISED PATCH 2/6] Introduce commit notes

From: Adam Hayek <adam.hayek@gmail.com>
Date: Jul 19, 2007, 09:57 UTC
Message-ID: <46aec1580707190257i6e2f7e4bte61748a67549e434@mail.gmail.com>
In-Reply-To: <7vodi83fg7.fsf@assigned-by-dhcp.cox.net>

On 7/19/07, Junio C Hamano <gitster@pobox.com> wrote:

Show 8 quoted lines

> Side note: I also think adding "extension section" to tree
> object is not a good idea to begin with.  The data nor length of
> such a section cannot participate in hash computation to derive
> the tree's object name so that we can still compare two tree
> objects (with and without such extension) that have the same
> contents by only looking at their object names.  But having
> contents that are not counted as parts of the object's name goes
> against the reliability and safety of git.

Excuse me for being brand new to this list and to git itself, but if the issue is where to put "extra" data to go along with a given object there should be a relatively simple way to do it. If your object's hash/name is X, take the string ("%s-extra", X), hash that, and use the resulting hash as the name of the file to store whatever extra data you have. There would be the issue of when and how to move this new file when the original file is moved, but old versions of git at least wouldn't break, they'd just never know about the extra data in the separate file. Of course you could do endless variations of this to store whatever classes of extra data separately.