From: Gioele Barabucci <gioele@svario.it>
To: John Keeping <john@keeping.me.uk>
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 21:03:19 +0200 [thread overview]
Message-ID: <51A25C77.6040205@svario.it> (raw)
In-Reply-To: <20130526190019.GM27005@serenity.lan>
Il 26/05/2013 21:00, John Keeping ha scritto:
>> Regardless of the implementation of the commands, if I do
>>
>> mkdir projectA
>> cd projectA
>> git init .
>> git remote add origin remote-repo/projectA.git
>> git pull origin master
>>
>> I get a working repository. If I do
>>
>> git clone remote-repo/projectA.git
>>
>> all I will get is an error.
>
> So the problem is that "git clone" does not seem to perform normal
> remote processing if you give it something that looks like a path.
I understand the problem. In the original email that started this thread
I asked for...
> I suppose that git interprets the argument as a local directory. Git
> should see if the argument matches one of the known URLs before
> raising an error.
I think all the paths should mean the same in every git command. In this
case, checking for insteadOf URLs before failing would solve this problem.
Regards,
--
Gioele Barabucci <gioele@svario.it>
next prev parent reply other threads:[~2013-05-26 19:03 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
2013-05-26 18:21 ` Gioele Barabucci
2013-05-26 19:00 ` John Keeping
2013-05-26 19:03 ` Gioele Barabucci [this message]
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=51A25C77.6040205@svario.it \
--to=gioele@svario.it \
--cc=git@vger.kernel.org \
--cc=gitter.spiros@gmail.com \
--cc=john@keeping.me.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox