git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Santi Béjar" <sbejar@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Junio C Hamano" <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [RFC] git-remote
Date: Fri, 5 Jan 2007 20:53:22 +0100	[thread overview]
Message-ID: <8aa486160701051153h52a93c16k2b190f58e652cb2e@mail.gmail.com> (raw)
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

  reply	other threads:[~2007-01-05 19:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-03 21:40 [RFC] git-remote Junio C Hamano
2007-01-03 22:05 ` Jakub Narebski
2007-01-05  3:02 ` Shawn O. Pearce
2007-01-05  3:07   ` Junio C Hamano
2007-01-05  3:17     ` Shawn O. Pearce
2007-01-05 12:59 ` Santi Béjar
2007-01-05 13:53   ` Johannes Schindelin
2007-01-05 19:53     ` Santi Béjar [this message]
2007-01-05 21:08       ` Carl Worth
2007-01-06  1:59         ` Junio C Hamano
2007-01-08 22:52           ` Carl Worth
2007-01-09  4:28 ` J. Bruce Fields
2007-01-09  5:48   ` Junio C Hamano
2007-01-09  5:50   ` Junio C Hamano
2007-01-09  9:22     ` Andreas Ericsson
2007-01-10 18:13       ` J. Bruce Fields

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=8aa486160701051153h52a93c16k2b190f58e652cb2e@mail.gmail.com \
    --to=sbejar@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).