Re: Get rid of .git/branches/ and .git/remotes/?
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Nov 22, 2005, 17:56 UTC
- Message-ID
- <Pine.LNX.4.63.0511221854120.27872@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <200511221831.03954.Josef.Weidendorfer@gmx.de>
Hi,
On Tue, 22 Nov 2005, Josef Weidendorfer wrote:
Show 10 quoted lines
> [remote:origin] > url = master.kernel.org:/pub/scm/git/git.git > pull = master:origin > > For this, the parser could return > remote.url = master.kernel.org:/pub/scm/git/git.git for origin > remote.pull = master:origin for origin > > By introducing such a scheme, multi-value vars would fit perfectly > for use for .git/remotes or .git/branches.
I don't know if you missed it, but hierarchical config keys were introduced by b17e659dd4007cb1d3eb5ac32b524c0c5ab59601:
[remote.origin] url = master.kernel.org:/pub/scm/git/git.git pull = master:origin
is parsable by
git-config-set --get remote.origin.url
now.
Hth, Dscho