From: Junio C Hamano <gitster@pobox.com>
Date: Mon, 22 Apr 2013 16:00:00 GMT
Subject: Re: [BUG] Filenames with single colon being treated as remote repository
Message-ID: <7vobd6pncv.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20130422153516.GB11886@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

> So I think one reasonable path would be:
>
>   1. Do not treat "host:path" as ssh if "host" has a slash, which should
>      not regress anybody. It does not allow unadorned relative paths
>      with colons, but it lets you use absolute paths or "./" to
>      disambiguate.
>
>   2. Teach git-clone to ask the transport code to parse the source repo
>      spec, and decide from that whether it is local or not. That would
>      harmonize the implementations and avoid errors when you _did_ mean
>      to use ssh, but "host:path" happens to exist in your filesystem. I
>      also would not be surprised if there are problems with
>      URL-encoding, but maybe clone handles that properly (I didn't
>      check).
>
> And the "host contains slash" rule is pretty easy to explain in the
> documentation, which is good.

Sounds like a good direction to take us.