Re: Storing state in $GIT_DIR

From: Daniel Barkalow <barkalow@iabervon.org>
Date: Aug 26, 2005, 05:08 UTC
Message-ID: <Pine.LNX.4.63.0508260101390.23242@iabervon.org>
In-Reply-To: <7v3boxl3o1.fsf@assigned-by-dhcp.cox.net>

On Thu, 25 Aug 2005, Junio C Hamano wrote:

Show 6 quoted lines

> Now, among the existing object types, there are only two kinds
> of objects you can use for this.  If the only thing you need to
> record is some textual information with one pointer to git
> branch head, then you can use tag that points at the git head,
> and store everything else as the tag comment.  This is doable
> but unwieldy.

I don't think this buys you anything, because then the tag needs to be accessible from something, which is the same problem you were trying to solve for the commit.

> You could abuse a commit object as well; you store commit
> objects (such as the corresponding git branch head) as parent
> commits, and put everything else in a tree that is associated
> with that commit.

If you want to go that way, you could add a new field to commits with minimal effort: you just need to parse it in commit.c, generate it in git-commit-tree (with an option), and pull it in pull.c, and everything should work as far as making the git portion follow the metadata around.

	-Daniel
*This .sig left intentionally blank*