Re: [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config

From: Petr Baudis <pasky@suse.cz>
Date: Nov 28, 2005, 13:59 UTC
Message-ID: <20051128135915.GR22159@pasky.or.cz>
In-Reply-To: <Pine.LNX.4.63.0511280248020.12343@wbgn013.biozentrum.uni-wuerzburg.de>

Dear diary, on Mon, Nov 28, 2005 at 02:52:08AM CET, I got a letter where Johannes Schindelin <Johannes.Schindelin@gmx.de> said that...

Show 6 quoted lines

> On Sun, 27 Nov 2005, Petr Baudis wrote:
> 
> > I've tried to explain that branches and remotes are different concepts,
> 
> Well, no. They aren't. The "branches" concept is a proper special case of 
> the "remotes" concept.

Yes, but precisely what I want to do is to avoid (most of) the "added value" of the remotes concept, if you will. Also, it really is a different namespace than branches (while branches share the same namespace with heads); I can try to make the namespaces match, but when they suddenly won't, you are in big mess.

Show 8 quoted lines

> But what the heck, I don't care what you eventually use.
> 
> I only realized that we -- in the good tradition of UNIX -- have many 
> different formats for different configurations: Some configurations are in 
> .gitignore, some are in .git/branches/, some in .git/remotes/, some in 
> .git/config, and even some in environment variables!
> 
> If everybody says that this should stay so, I'll just shut up.

As I said, I don't care much if this moves to the git configuration file, but please don't merge it with the remotes.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.