From: Jonathan Nieder <jrnieder@gmail.com>
To: "Kyle J. McKay" <mackyle@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: git_inetd_server: run git-http-backend using inetd
Date: Fri, 18 Jul 2014 10:16:35 -0700 [thread overview]
Message-ID: <20140718171635.GR12427@google.com> (raw)
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
next prev parent reply other threads:[~2014-07-18 17:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 21:28 git_inetd_server: run git-http-backend using inetd Kyle J. McKay
2014-07-17 22:10 ` Jonathan Nieder
2014-07-17 23:38 ` Kyle J. McKay
2014-07-18 2:22 ` Jonathan Nieder
2014-07-18 6:48 ` Kyle J. McKay
2014-07-18 17:16 ` Jonathan Nieder [this message]
2014-07-19 0:08 ` Kyle J. McKay
2014-07-19 0:19 ` Jonathan Nieder
2014-07-19 1:54 ` Kyle J. McKay
2014-07-19 6:21 ` Torsten Bögershausen
2014-07-19 17:06 ` Jonathan Nieder
2014-07-20 6:10 ` Torsten Bögershausen
2014-07-20 15:25 ` 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=20140718171635.GR12427@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=mackyle@gmail.com \
/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 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 NNTP newsgroup(s).