From: Eli Schwartz <firstname.lastname@example.org> To: Jonathan Nieder <email@example.com> Cc: "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, 31 Mar 2021 00:23:57 -0400 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <YFJ/g2N+s1V3/qMo@google.com> [-- Attachment #1.1: Type: text/plain, Size: 1931 bytes --] On 3/17/21 6:15 PM, Jonathan Nieder wrote: > Hi, > > Eli Schwartz wrote: > >> I'm not especially attached to the proposal. I'm a maintainer for one >> of these package managers that currently special-case git+https?:// and >> rewrite the url that git sees, which has worked adequately for a long >> time. > > 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://? https://archlinux.org/pacman/PKGBUILD.5.html#VCS We support cloning arbitrary version controlled sources via either vcs:// or vcs+proto:// but not proto+vcs:// so that encompasses git:// or git+https:// or git+ssh:// and also permits hg+https or svn+https:// or bzr+http:// or fossil+https:// (ignore the documentation not mentioning fossil, this is a development branch addition and obviously the docs are for the stable release) We then do prefix removal of everything before the plus sign since currently no VCS supports this directly (I think?), but we could remove that pass from our git source plugin if git implemented it internally. Implementing https+git:// as a synonym for https:// is IMO confusing, so I don't intend to implement it even if git does. I think one way to specify the VCS + transport protocol is enough... and prefix removal is easier than removing the middle of the string. The net effect would be, I guess, less code in the package manager, and users would be able to go to a public registry of source packages like https://aur.archlinux.org/packages/pacman-git, see the clickable link under "Sources (5)" and copy/paste that into a `git clone` command line without knowing they need to edit the link first. -- Eli Schwartz Arch Linux Bug Wrangler and Trusted User [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-31 4:25 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 [this message] 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 \ --firstname.lastname@example.org \ --email@example.com \ --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).