From: "Drew DeVault" <firstname.lastname@example.org> To: "Jonathan Nieder" <email@example.com> Cc: <firstname.lastname@example.org> Subject: Re: Regarding the depreciation of ssh+git/git+ssh protocols Date: Mon, 15 Mar 2021 14:14:31 -0400 [thread overview] Message-ID: <C9Y4NXXX6HRI.1IROIK8ZXK4S2@taiga> (raw) In-Reply-To: <YE+ftT2WaKDzcemail@example.com> On Mon Mar 15, 2021 at 1:56 PM EDT, Jonathan Nieder wrote: > The original idea of URI schemes like svn+https is that we can treat > these version control URLs as part of the general category of uniform > resource identifiers --- in other words, you might be able to type > them in a browser's URL bar, browse the content of a repository, use > an <img> tag to point to a file within a version control repository, > and so on. That was indeed the original idea, but I think it's fair to assume that it's evolved well beyond this. There are many schemes in common use which don't meet this criteria, such as mailto:, magnet:, bitcoin:, postgresql:, and so on. None of these examples make productive use of all of the URI, such as your fragment example, but they still make productive use of parts of the URI. To my mind, the contemporary purpose of a URI is to: 1. Identify a resource 2. Identify the protocol used to access it 3. Store domain-specific information that an implementation of that protocol can use to accomplish something > The missing piece is an HTTP header to unambiguously mark that URL as > being usable by Git. I'm not aware of a standard way to do that; e.g. > golang's "go get" tool[*] uses a custom 'meta name="go-import"' HTML > element. I don't agree that this is the case. It would be much better to be able to identify a URL as being useful for git without having to perform a network request to find out. A standard approach to the go-import kind of deal is also a meritous idea, but a separate matter - and one I'm also involved in trying to address!
next prev parent reply other threads:[~2021-03-15 18:15 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-15 16:27 Drew DeVault 2021-03-15 17:56 ` Jonathan Nieder 2021-03-15 18:14 ` Drew DeVault [this message] 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 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
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=C9Y4NXXX6HRI.1IROIK8ZXK4S2@taiga \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Regarding the depreciation of ssh+git/git+ssh protocols' \ /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
Code repositories for project(s) associated with this 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).