From: "Drew DeVault" <firstname.lastname@example.org> To: "Jonathan Nieder" <email@example.com> Cc: "brian m. carlson" <firstname.lastname@example.org>, <email@example.com> Subject: Re: Regarding the depreciation of ssh+git/git+ssh protocols Date: Mon, 15 Mar 2021 21:05:34 -0400 [thread overview] Message-ID: <C9YDEO8Z8J96.262IOS9IW6F39@taiga> (raw) In-Reply-To: <YFADuptwV7iR76g5@google.com> On Mon Mar 15, 2021 at 9:02 PM EDT, Jonathan Nieder wrote: > I'm not sure it's a disconnect; instead, it just looks like we > disagree. That said, with more details about the use case it might be > possible to sway me in another direction. > > To maintain the URI analogy: the URI does not tell me the content-type > of what I can access from there. Until I know that content-type, I > may not know what the best tool is to access it. git isn't a content type, it's a protocol. git over HTTP or git over SSH is a protocol in its own right, distinct from these base protocols, in the same sense that SSH lives on top of TCP which lives on top of IP which is transmitted to your computer over ethernet or 802.11. It's turtles all the way down. > The root of the disagreement, though, is "Git URLs" looking like a URI > in the first place. They're not meant to be universal at all. They > are specifically for Git. At worst I would call this a happy coincidence. We have this convenient universal format at our disposal, and we would be wise to take advantage of it. Rejecting it on the premise that we never wanted to have it doesn't make sense when we consider that (1) we do have it and (2) it can be of good use to us.
next prev parent reply other threads:[~2021-03-16 1:16 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 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 [this message] 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=C9YDEO8Z8J96.262IOS9IW6F39@taiga \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --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).