From: "Torsten Bögershausen" <tboegi@web.de>
To: "Jeff King" <peff@peff.net>, "Torsten Bögershausen" <tboegi@web.de>
Cc: Duy Nguyen <pclouds@gmail.com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] clone: local URLs are not for ssh
Date: Tue, 15 Oct 2013 09:22:46 +0200 [thread overview]
Message-ID: <525CED46.3050006@web.de> (raw)
In-Reply-To: <20131015001259.GB10415@sigill.intra.peff.net>
On 15.10.13 02:12, Jeff King wrote:
> On Sun, Oct 13, 2013 at 10:00:12PM +0200, Torsten Bögershausen wrote:
>
>> On 05.10.13 21:48, Torsten Bögershausen wrote:
>>> On 2013-10-03 03.31, Jeff King wrote:
>>>>
>>>> http://article.gmane.org/gmane.comp.version-control.git/235473
>> What do we think about extending the test a little bit:
>
> I never mind more tests, but note that my tests are now part of Duy's
> 8d3d28f, so you would want to build on top.
>
>> diff --git a/t/t5602-clone-remote-exec.sh b/t/t5602-clone-remote-exec.sh
>> index 3f353d9..790896f 100755
>> --- a/t/t5602-clone-remote-exec.sh
>> +++ b/t/t5602-clone-remote-exec.sh
>
> Mine were in t5601...should these go there, too, or is there a reason to
> do it in t5602?
I confused 5601 with 5602, started from there, ended up in a mess.
Thanks for saving me.
Using the comments, I'll send a real patch on top of pu.
/Torsten
prev parent reply other threads:[~2013-10-15 7:23 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
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 [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=525CED46.3050006@web.de \
--to=tboegi@web.de \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).