From: "Drew DeVault" <sir@cmpwn.com>
To: "Jakub Narębski" <jnareb@gmail.com>
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:53:07 -0400 [thread overview]
Message-ID: <C9ZPMTQD2PJE.3N2S1VX9NVK2T@taiga> (raw)
In-Reply-To: <85r1kewqui.fsf@gmail.com>
On Tue Mar 16, 2021 at 8:45 PM EDT, Jakub Narębski wrote:
> Well, thara is a total of one protocol (CoAP) that uses '+' based
> schemas, namely: coap+tcp, coap+ws, coaps+tcp, coaps+ws (well at least
> out of those protocols that made it into IANA).
One is greater than zero! It is blessed, even if only a little. We can
just go ask the IANA about it if we want to further entertain the idea
that this approach is non-kosher, but, like you said: if the RFC states
it, then it is a standard construct.
> Though it in this case neither of those parts of schema joined by the
> '+' sign is an application name...
git is both an application name and a protocol name. ¯\_(ツ)_/¯
> > Aye, people do expect it to work. The problem is not going to go away.
>
> To reiterate, the idea of "prefixed URLs", that is using git+https://
> and git+ssh:// is to denote that said URL is only usable by Git, without
> any additional out-of-band information (like other attributes on <a>
> element or its encompassing element)?
Correct.
next prev parent reply other threads:[~2021-03-17 15:53 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
2021-03-17 0:45 ` Jakub Narębski
2021-03-17 14:53 ` Drew DeVault [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C9ZPMTQD2PJE.3N2S1VX9NVK2T@taiga \
--to=sir@cmpwn.com \
--cc=eschwartz@archlinux.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=jrnieder@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).