From: Jonathan Nieder <jrnieder@gmail.com>
To: Eli Schwartz <eschwartz@archlinux.org>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
Drew DeVault <sir@cmpwn.com>,
git@vger.kernel.org
Subject: Re: Regarding the depreciation of ssh+git/git+ssh protocols
Date: Wed, 17 Mar 2021 15:15:31 -0700 [thread overview]
Message-ID: <YFJ/g2N+s1V3/qMo@google.com> (raw)
In-Reply-To: <8fed0d1f-a2bd-131c-5552-e95216b43474@archlinux.org>
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://?
Thanks,
Jonathan
next prev parent reply other threads:[~2021-03-17 22:16 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YFJ/g2N+s1V3/qMo@google.com \
--to=jrnieder@gmail.com \
--cc=eschwartz@archlinux.org \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
--cc=sir@cmpwn.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.