From: Mark Lodato <email@example.com> To: Jonathan Nieder <firstname.lastname@example.org> Cc: Eli Schwartz <email@example.com>, "brian m. carlson" <firstname.lastname@example.org>, Drew DeVault <email@example.com>, firstname.lastname@example.org Subject: Re: Regarding the depreciation of ssh+git/git+ssh protocols Date: Wed, 7 Apr 2021 09:46:46 -0400 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <YFJ/g2N+s1V3/qMo@google.com> Jonathan Nieder wrote: > This is useful context. What URL forms does this package manager > support (e.g., do you have a link to its documentation)? What would > the effect be for the package manager and its users if Git started > supporting a git+https:// synonym for https://? Here are two more examples: - pip: https://pip.pypa.io/en/latest/cli/pip_install/#git - SPDX: https://spdx.github.io/spdx-spec/3-package-information/#37-package-download-location The common thread is that systems need a way to uniquely identify a git repository or some object therein. I believe this means some combination of: - VCS type (git) - Transport location (e.g. https://github.com/git/git) - Ref (e.g. master) - Resolved commit ID (e.g. 48bf2fa8bad054d66bd79c6ba903c89c704201f7) - Path (e.g. contrib/diff-highlight) - (possibly) Clone depth As Drew has said, the current state of affairs is that, lacking a standard, multiple systems are all inventing incompatible schemes using the `git+https` name. This is not a good situation because the "URI" is no longer "unique". Given such a URI in isolation, one cannot know how to parse it. It's not clear to me that git itself needs to support this scheme. It would go a long way for git to simply recommend a particular scheme so that all these systems can use a common format. (We could register that with IANA.) The pip format seems to be the closest, but it doesn't support both ref AND resolved commit ID, and it is currently specific to pip (`egg=` could be replaced with `path=`). Best, Mark
next prev parent reply other threads:[~2021-04-07 13:46 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 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 [this message] 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --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).