From: "Torsten Bögershausen" <tboegi@web.de>
To: "Duy Nguyen" <pclouds@gmail.com>, "Torsten Bögershausen" <tboegi@web.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] clone: local URLs are not for ssh
Date: Wed, 02 Oct 2013 20:40:05 +0200 [thread overview]
Message-ID: <524C6885.8020602@web.de> (raw)
In-Reply-To: <CACsJy8B-wA=bX6+E6O6UvX2vEtOwnR1PCMZNoi-q0x_jacB89Q@mail.gmail.com>
On 2013-09-29 02.33, Duy Nguyen wrote:
> On Sun, Sep 29, 2013 at 2:37 AM, Torsten Bögershausen <tboegi@web.de> wrote:
>> "git clone /foo/bar:baz" or "git clone ../foo/bar:baz"
>> are meant to clone from the local file system, and not to clone
>> from a remote server over git-over-ssh.
>
> I don't think this is necessary. Commit 6000334 should detect both
> cases fine because both have a slash before the first colon.
Sorry for the noise, I noticed it when I was trying to construct test cases.
What do we think about adding this at the end of t5505:
test_expect_success 'fetch fail [noexistinghost0:2223]:blink.git' '
(
! git fetch [noexistinghost0:2223]:blink.git 2>err &&
grep ssh err &&
rm err
)
'
test_expect_success 'fetch fail noexistinghost1:2223:blink.git' '
(
! git fetch "noexistinghost1:2223:blink.git" 2>err &&
grep ssh err &&
rm err
)
'
test_expect_success 'fetch fail noexistinghost2:2223' '
(
! git fetch "noexistinghost2:2223" 2>err &&
grep ssh err &&
rm err
)
'
test_expect_success 'fetch fail ./noexistinghost4:2223"' '
(
! git fetch "./noexistinghost4:2223" 2>err &&
grep "does not appear to be a git repository" err &&
rm err
)
'
next prev parent reply other threads:[~2013-10-02 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-28 19:37 [PATCH] clone: local URLs are not for ssh Torsten Bögershausen
2013-09-29 0:33 ` Duy Nguyen
2013-10-02 18:40 ` Torsten Bögershausen [this message]
2013-10-03 1:01 ` Duy Nguyen
2013-10-03 1:31 ` Jeff King
2013-10-05 19:48 ` Torsten Bögershausen
2013-10-05 20:35 ` Matthieu Moy
2013-10-13 20:00 ` Torsten Bögershausen
2013-10-15 0:12 ` Jeff King
2013-10-15 7:22 ` Torsten Bögershausen
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=524C6885.8020602@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/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.