Re: [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Nov 28, 2005, 16:29 UTC
- Message-ID
- <Pine.LNX.4.63.0511281728110.11362@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <7vfyph1ebq.fsf@assigned-by-dhcp.cox.net>
Hi,
On Sun, 27 Nov 2005, Junio C Hamano wrote:
Show 19 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes: > > > 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! > > Can you live with something like this? > > - we will add new ones to config, now we have it; > > - we will not deprecate existing ones outside of config for some time; > > - we will not duplicate/move existing ones into config at least > for now to keep our work less complicated; > > - we would revisit deprecating things outside config file > sometime later after 1.0 stabilizes, and that's when we will > talk about moving these things into config.
I can very well live with this!
As a first step, we could support getting the remote information from .git/config after testing .git/branches/ and .git/remotes/?
Ciao, Dscho