From: "Drew DeVault" <sir@cmpwn.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>, <git@vger.kernel.org>
Subject: Re: Regarding the depreciation of ssh+git/git+ssh protocols
Date: Mon, 15 Mar 2021 20:52:01 -0400 [thread overview]
Message-ID: <C9YD4AEUH84L.29FP64NJJ1BPU@taiga> (raw)
In-Reply-To: <YE/ZSiuIsMs3ucVM@camp.crustytoothpaste.net>
On Mon Mar 15, 2021 at 6:01 PM EDT, brian m. carlson wrote:
> But you can't find whether a URL is useful for a particular purpose in
> general. For example, if I see an HTTPS URL, that tells me nothing
> about the resources that one might find at that URL.
>
> In addition, it's possible that the data you want exists, but is not
> suitable for you in whatever way (not in a language you understand, in
> an unsuitable format, is illegal or offensive, etc.), or you are not
> authorized to access it. You can't know any of this without making some
> sort of request.
>
> All a URL can tell you is literally where a resource is located. Even
> if we saw a URL that used the hypothetical https+git as the scheme, we
> couldn't determine whether we could access the data, whether the data
> even still exists, or, even if we knew all of those things, whether it
> was using the smart or dumb protocol, without making a request.
What we know is that we can pass it to git to deal with, and then git
will determine the next steps. It will negotiate dumb or smart HTTP
in-band, deal with errors that arise, and so on. It signals that git is
the tool best equipped to deal with the situation, and without that we'd
end up guessing.
> So I don't think this is a thing we can do, simply because in general
> URLs aren't suitable for sharing this kind of information.
That's simply not true. They are quite capable at this task, and are
fulfilling this duty for a wide varitety of applications today.
I don't really understand the disconnect here. No, URLs are not magic,
but they are perfectly sufficient for this use-case.
next prev parent reply other threads:[~2021-03-16 0: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 [this message]
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
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=C9YD4AEUH84L.29FP64NJJ1BPU@taiga \
--to=sir@cmpwn.com \
--cc=git@vger.kernel.org \
--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).