From: Santi Béjar <sbejar@gmail.com>
Date: Fri, 05 Jan 2007 19:53:22 GMT
Subject: Re: [RFC] git-remote
Message-ID: <8aa486160701051153h52a93c16k2b190f58e652cb2e@mail.gmail.com>
In-Reply-To: <Pine.LNX.4.63.0701051448560.22628@wbgn013.biozentrum.uni-wuerzburg.de>

On 1/5/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Fri, 5 Jan 2007, Santi Béjar wrote:
>
> > * In "git remote add <name> <remote>": git could use the remote url to
> > deduce a <name>, like what git-clone does.
>
> That does not make any sense. For example, I track
> "git://git.kernel.org/.../git.git" and "192.168.0.128:gits/git.git".
> Something very similar applies to the host name: if you track multiple
> Linux repos, chances are that most of them are on git.kernel.org.
>
> I guess _if_ you have more than one upstream you are tracking (which is
> not the most common case, but hey, git-remote is for exactly that case) it
> is not uncommon to have similar urls.
>
> IMHO Junio's proposal is as good as it gets.
>

I was talking about the default name, so you could do:

$ git clone\
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
$ cd linux-2.6
$ git remote add \
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-2.6.git
$ git remote show libata-2.6

Santi