From: John Keeping <john@keeping.me.uk>
To: Gioele Barabucci <gioele@svario.it>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Elia Pinto <gitter.spiros@gmail.com>,
git@vger.kernel.org
Subject: Re: git clone does not understand insteadOf URLs
Date: Sun, 26 May 2013 19:14:31 +0100 [thread overview]
Message-ID: <20130526181430.GL27005@serenity.lan> (raw)
In-Reply-To: <51A24FF4.4010102@svario.it>
On Sun, May 26, 2013 at 08:09:56PM +0200, Gioele Barabucci wrote:
> Il 26/05/2013 20:00, Andreas Schwab ha scritto:
> >> Simple, I keep all my projects on the same server, so I would like to
> >> refer to that server + path using 'remote-repo'.
> >>
> >> "git+ssh://git.example.org//users/gioele/projects" insteadOf "remote-repo"
> >
> > You can use "remote-repo:" instead.
>
> Do you mean I could use
> "git+ssh://git.example.org//users/gioele/projects" insteadOf
> "remote-repo:"? Yes, but now I have dozens of repositories already set
> up in various workstations and I do not want to go and change all of them.
>
> What really bugs me is the fact that `git clone` and `git remote add`
> parse the same path in different ways. Git already has many
> inconsistencies. This one can be easily ironed out.
In what way do you think that `git remote add` handles the path?
All `git remote add` does is add a new "remote.<name>.url" entry to the
configuration file with the value as given on the command line. The
insteadOf mapping will only be applied when you try to fetch from/push
to the remote.
next prev parent reply other threads:[~2013-05-26 18:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 20:23 git clone does not understand insteadOf URLs Gioele Barabucci
2013-05-26 15:13 ` Elia Pinto
2013-05-26 17:55 ` Gioele Barabucci
2013-05-26 18:00 ` Andreas Schwab
2013-05-26 18:09 ` Gioele Barabucci
2013-05-26 18:14 ` John Keeping [this message]
2013-05-26 18:21 ` Gioele Barabucci
2013-05-26 19:00 ` John Keeping
2013-05-26 19:03 ` Gioele Barabucci
2013-05-28 20:06 ` Junio C Hamano
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=20130526181430.GL27005@serenity.lan \
--to=john@keeping.me.uk \
--cc=gioele@svario.it \
--cc=git@vger.kernel.org \
--cc=gitter.spiros@gmail.com \
--cc=schwab@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.