On Mon, Nov 09, 2015 at 06:49:35PM +0100, Dennis Kaarsemaker wrote:
> When passed an ssh:// url, git strips ssh://host from the url but does
> not remove leading slashes from the path. So when this test used
> ssh://remote//path/to/pwd, the path accessed by our fake SSH is
> //path/to/pwd, which c
When passed an ssh:// url, git strips ssh://host from the url but does
not remove leading slashes from the path. So when this test used
ssh://remote//path/to/pwd, the path accessed by our fake SSH is
//path/to/pwd, which cygwin interprets as a UNC path, causing the test
to fail.
We may want to act
On Sun, Nov 08, 2015 at 10:54:04AM +0100, Dennis Kaarsemaker wrote:
> The fake ssh used by this test simply strips ssh://host from the url,
> leaving paths behind that start with //, which cygwin interprets as UNC
> paths, causing the test to fail.
I found the first sentence a little misleading.
The fake ssh used by this test simply strips ssh://host from the url,
leaving paths behind that start with //, which cygwin interprets as UNC
paths, causing the test to fail.
We may want to actually fix this in git itself, making it remove extra
slashes from urls before feeding them to transports
4 matches
Mail list logo