From: Johannes Sixt <j.sixt@viscovery.net>
To: "Torsten Bögershausen" <tboegi@web.de>, git@vger.kernel.org
Subject: Re: [PATCH V4] git clone: is an URL local or ssh
Date: Tue, 05 Nov 2013 08:14:45 +0100 [thread overview]
Message-ID: <52789AE5.2010702@viscovery.net> (raw)
In-Reply-To: <201311042220.50178.tboegi@web.de>
Am 11/4/2013 22:20, schrieb Torsten Bögershausen:
> Bug fix for msygit in t5601 : use $PWD insted of $(pwd)
Not really. $PWD is /c/foo/bar style, but $(pwd) is c:/foo/bar, which is
equally good.
> test_expect_success 'clone with excess parameters (2)' '
>
> rm -fr dst &&
> - test_must_fail git clone -n "file://$(pwd)/src" dst junk
> + test_must_fail git clone -n "file://$PWD/src" dst junk
That the code change necessitates this change in the test suite is a sign
that there is something wrong with the new code.
And indeed, the original works:
C:\Temp\gittest>git clone -n file://c:/Temp/gittest/foo good
Cloning into 'good'...
remote: Counting objects: 2, done.
remote: Total 2 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (2/2), done.
Checking connectivity... done.
but the changed code does not:
C:\Temp\gittest>D:\src\mingw-git\git clone -n file://c:/Temp/gittest/foo bad
Cloning into 'bad'...
fatal: 'D:/Src/MsysGit/Temp/gittest/foo' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Can you please make this into a series of small patches so that we can
more easily see the good and the bad parts? One of the patches could be a
clean-up of the current protocol determination and URL dissection, which
is indigestible spaghetti right now.
-- Hannes
next prev parent reply other threads:[~2013-11-05 7:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 21:20 [PATCH V4] git clone: is an URL local or ssh Torsten Bögershausen
2013-11-05 7:14 ` Johannes Sixt [this message]
2013-11-05 19:35 ` [PATCH 1/2] git_connect: remove artificial limit of a remote command Johannes Sixt
2013-11-05 19:39 ` [PATCH 2/2] git_connect: factor out discovery of the protocol and its parts Johannes Sixt
2013-11-05 20:45 ` Torsten Bögershausen
2013-11-05 21:22 ` Johannes Sixt
2013-11-06 15:31 ` Torsten Bögershausen
-- strict thread matches above, loose matches on Subject: below --
2013-11-04 21:18 [PATCH V4] git clone: is an URL local or ssh Torsten Bögershausen
2013-11-04 21:04 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=52789AE5.2010702@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/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.