Re: [PATCH] Use new .git/config for storing "origin" shortcut repository

From: Shawn Pearce <spearce@spearce.org>
Date: Nov 26, 2006, 03:02 UTC
Message-ID: <20061126030209.GA29394@spearce.org>
In-Reply-To: <200611260003.31025.andyparkins@gmail.com>

Andy Parkins <andyparkins@gmail.com> wrote:

Show 19 quoted lines

> If .git/remotes/ is now deprecated, then git-clone shouldn't use it.
> This patch adds the analogous definitions to .git/config using
> git-repo-config calls.
> 
> For example what was previously .git/remotes/origin
>   URL: proto://host/path
>   Pull: refs/heads/master:refs/heads/origin
> Is now added to .git/config as
>   [remote "origin"]
>   url = proto://host/path
>   fetch = refs/heads/master:refs/heads/origin
> 
> Signed-off-by: Andy Parkins <andyparkins@gmail.com>
> ---
> I'm not sure if I'm correct in thinking that .git/remotes is deprecated.  If it is,
> this patch makes git-clone use .git/config instead.
> 
> Personally I like it, I think there should be as small a number of places for 
> configuring the repository as possible.

I agree. There's all sorts of advantages to setting up remotes by the config file. Its also easier to load and work with in git-gui. :-)

I've switched to the config file syntax completely, and a few folks I work with have done the same, citing that it is easier to have everything in one file.