From: Jonathan Nieder <jrnieder@gmail.com>
Date: Fri, 18 Jul 2014 17:16:35 GMT
Subject: Re: git_inetd_server: run git-http-backend using inetd
Message-ID: <20140718171635.GR12427@google.com>
In-Reply-To: <50047EE8-4EF8-49E3-9067-1C88B2FB9D58@gmail.com>

Kyle J. McKay wrote:

> You might also want to take a look at [1] which suggests that when
> doing SRV lookups for URLs they should be done regardless of whether
> or not a port number is present (which then eliminates the RFC 3986
> issue the current SRV lookup code has).

"Git URLs" as described e.g. in git-clone(1) weren't intended to be
actual URIs.  What would be the interoperability advantage of making
them URIs?

This has come up before, with e.g. people asking to introduce a
git+ssh:// and git+http:// syntax to refer to repositories accessed
using those transports without conflicting with the usual meanings of
ssh:// and http://.  If there's a good use case for that, maybe it
would be worth doing some day.

Curious,
Jonathan