Re: What is in git.git

From: Petr Baudis <pasky@suse.cz>
Date: 2006-01-22 14:12:37
Just-in-case panic response...

Dear diary, on Sun, Jan 22, 2006 at 12:33:25AM CET, I got a letter
where Josef Weidendorfer <Josef.Weidendorfer@gmx.de> said that...
> > You need to keep a file that describes how your repository is
> > tracking the development histories of each subproject in
> > $GIT_DIR/bind, that would look like:
> > 
> > 	master main=/ subpro=sub/
> 
> What about putting $GITDIR/bind information directly into reference files?
> 
>  $HOME/gitproj> cat .git/refs/heads/master
>  92347432598...
>  bind main=/
>  bind subpro=sub/
> 
> This way, you can rename/copy heads, and the binding info will stay with
> the commit.

Please don't. I can see no real advantage to separate files (except for
the very rare case of rename/copy/removal of heads) except for massive
porcelain breakage and significant clutter-up of all the code dealing
with refs.

Please leave our poor refs alone. :) They are fine as they are - simple
one-value thing.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Of the 3 great composers Mozart tells us what it's like to be human,
Beethoven tells us what it's like to be Beethoven and Bach tells us
what it's like to be the universe.  -- Douglas Adams
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Sun Jan 22 14:11:41 2006

This archive was generated by hypermail 2.1.8 : 2006-01-22 14:11:50 EST