Re: What is in git.git

From: Junio C Hamano <junkio@cox.net>
Date: Jan 22, 2006, 20:08 UTC
Message-ID: <7vu0bwdo08.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.64.0601221106330.25300@iabervon.org>

Daniel Barkalow <barkalow@iabervon.org> writes:

> I think you're misunderstanding the use of the "bind" file or equivalent. 
>...
> So moving back to (A) wouldn't keep the binding point of subproject, 
> because it would rewrite bind to what it had been.

A lot better said than my version of the response.  Thanks.

Show 7 quoted lines

> I'm going to suggest again keeping this information in the index file (but 
> not in the index data structure, so the changes to the code are only in 
> the library routines to read and write the file, and, of course, anything 
> that's actually trying to manipulate the binding locations). I started 
> working on a patch to pu to skip S_IFDIR entries from the index file when 
> building the table in memory, and that was straightforward, but I got into 
> sysadmin issues when I was going to test giving it something to skip.

I have been thinking about this one, and having read that read-cache code I think the coding is not too involved.

My current inclination is to use the same version number (2) by default and promote it to a new version number (3) once you add subproject-binding information to the index file. Then current tools would keep working on repositories created or operated upon with the new tools, as long as the project does not use the new feature.