From: "Drew DeVault" <sir@cmpwn.com>
To: "Jeff King" <peff@peff.net>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
"Eli Schwartz" <eschwartz@archlinux.org>,
"Jonathan Nieder" <jrnieder@gmail.com>, <git@vger.kernel.org>
Subject: Re: Regarding the depreciation of ssh+git/git+ssh protocols
Date: Wed, 17 Mar 2021 10:50:15 -0400 [thread overview]
Message-ID: <C9ZPKMPKCQ9Y.X7U9IVV4A7NU@taiga> (raw)
In-Reply-To: <YFEjCU1jgrsPIhvk@coredump.intra.peff.net>
On Tue Mar 16, 2021 at 5:28 PM EDT, Jeff King wrote:
> Git remotes are most definitely not just URIs. Some valid remotes are:
> ".", "foo", "/tmp/foo", "c:\foo", "example.com:foo". The parser inside
> Git has rules to distinguish these from actual rfc3986-compliant URIs.
>
> Now I don't know much about the parsing code in, say, git-lfs, or how
> much of pain it would be to add a new scheme for something that _does_
> conform to rfc3986. But it's not necessarily as easy as "you should be
> using a compliant URI parser".
Sorry, I meant to say that git remotes are a superset of URIs, so a
conformant URI parser already has to be involved - I didn't mean that
all git remotes are URIs.
next prev parent reply other threads:[~2021-03-17 15:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 16:27 Regarding the depreciation of ssh+git/git+ssh protocols Drew DeVault
2021-03-15 17:56 ` Jonathan Nieder
2021-03-15 18:14 ` Drew DeVault
2021-03-15 22:01 ` brian m. carlson
2021-03-16 0:52 ` Drew DeVault
2021-03-16 1:02 ` Jonathan Nieder
2021-03-16 1:05 ` Drew DeVault
2021-03-16 21:23 ` Jeff King
2021-03-17 14:49 ` Drew DeVault
2021-03-18 21:30 ` Junio C Hamano
2021-03-18 21:53 ` Drew DeVault
2021-03-16 4:38 ` Eli Schwartz
2021-03-16 11:54 ` brian m. carlson
2021-03-16 14:21 ` Drew DeVault
2021-03-16 21:28 ` Jeff King
2021-03-17 14:50 ` Drew DeVault [this message]
2021-03-17 0:45 ` Jakub Narębski
2021-03-17 14:53 ` Drew DeVault
2021-03-17 22:06 ` brian m. carlson
2021-03-18 12:53 ` Drew DeVault
2021-03-16 18:03 ` Eli Schwartz
2021-03-17 22:15 ` Jonathan Nieder
2021-03-31 4:23 ` Eli Schwartz
2021-04-07 13:46 ` Mark Lodato
2021-04-07 19:46 ` Junio C Hamano
2021-04-13 8:52 ` Kerry, Richard
2021-03-16 0:54 ` Drew DeVault
2023-10-13 20:49 David Rogers
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=C9ZPKMPKCQ9Y.X7U9IVV4A7NU@taiga \
--to=sir@cmpwn.com \
--cc=eschwartz@archlinux.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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.