Re: Get rid of .git/branches/ and .git/remotes/?
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Nov 23, 2005, 15:08 UTC
- Message-ID
- <Pine.LNX.4.63.0511231553390.8191@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <438371E8.2030701@op5.se>
Hi,
On Tue, 22 Nov 2005, Andreas Ericsson wrote:
Show 7 quoted lines
> Johannes Schindelin wrote: > > > > git-config-set --get remote.origin.url > > > > So... "git-config-set" is used for both getting and setting? Why not just > "git-config --set" and "git-config --get" to make things a bit less confusing?
I tried to do this more like a proof of a concept (Yeah, famous last words...) and tried to be not so intrusive. There is already a config.c, and to keep with the naming, this would have to move to config-lib.c to make space for config.c which really is the source for git-config$(X).
Should we rename config.c to config-lib.c, and config-set.c to config.c? Personally, I think it too intrusive, but what the heck.
Ciao, Dscho