From: Shawn Pearce <spearce@spearce.org>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Use new .git/config for storing "origin" shortcut repository
Date: Sat, 25 Nov 2006 22:02:09 -0500 [thread overview]
Message-ID: <20061126030209.GA29394@spearce.org> (raw)
In-Reply-To: <200611260003.31025.andyparkins@gmail.com>
Andy Parkins <andyparkins@gmail.com> wrote:
> 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.
--
prev parent reply other threads:[~2006-11-26 3:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ekafpm@sea.gmane.org>
2006-11-26 0:03 ` [PATCH] Use new .git/config for storing "origin" shortcut repository Andy Parkins
2006-11-26 0:48 ` Johannes Schindelin
2006-11-26 3:52 ` Junio C Hamano
2006-11-26 13:45 ` Johannes Schindelin
2006-11-26 8:56 ` Andy Parkins
2006-11-26 9:15 ` Junio C Hamano
2006-11-26 9:35 ` Andy Parkins
2006-11-26 9:49 ` Jakub Narebski
2006-11-26 12:10 ` Andy Parkins
2006-11-26 13:30 ` Johannes Schindelin
2006-11-26 3:02 ` Shawn Pearce [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061126030209.GA29394@spearce.org \
--to=spearce@spearce.org \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).