From: Jeff King <peff@peff.net>
To: "Carlos Martín Nieto" <cmn@dwim.me>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Disown ssh+git and git+ssh
Date: Fri, 12 Feb 2016 13:40:24 -0500 [thread overview]
Message-ID: <20160212184023.GD19973@sigill.intra.peff.net> (raw)
In-Reply-To: <1455289777-186690-1-git-send-email-cmn@dwim.me>
On Fri, Feb 12, 2016 at 04:09:37PM +0100, Carlos Martín Nieto wrote:
> These were silly from the beginning, but we have to support them for
> compatibility. That doesn't mean we have to show them in the
> documentation. These were already left out of the main list, but a
> reference in the main manpage was left, so remove that.
Yeah, that reference was added by me to try to be thorough, but I think
mentioning ssh:// (as you do here) accomplishes the same goal in a
better way.
> Also add a note to discourage their use if anybody goes looking for them
> in the source code.
Sounds like a good plan.
> diff --git a/transport.c b/transport.c
> index 9ae7184..f5ae707 100644
> --- a/transport.c
> +++ b/transport.c
> @@ -1002,6 +1002,10 @@ struct transport *transport_get(struct remote *remote, const char *url)
> || starts_with(url, "file://")
> || starts_with(url, "git://")
> || starts_with(url, "ssh://")
> + /*
> + * These ssh schemes remain supported for compat but are
> + * undocumented and their use is discouraged
> + */
> || starts_with(url, "git+ssh://")
> || starts_with(url, "ssh+git://")) {
> /*
Breaking apart an ||-chain with a comment like this is a little odd, but
I think the result is reasonably readable, so it's probably OK.
The rest of the patch is obviously correct. Thanks for following up on
the earlier discussion.
-Peff
next prev parent reply other threads:[~2016-02-12 18:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 15:09 [PATCH] Disown ssh+git and git+ssh Carlos Martín Nieto
2016-02-12 18:40 ` Jeff King [this message]
2016-02-13 21:10 ` Junio C Hamano
2016-02-15 14:29 ` Carlos Martín Nieto
2016-02-15 18:16 ` Eric Sunshine
2016-03-09 21:56 ` Junio C Hamano
2016-03-10 20:51 ` Eric Sunshine
2016-03-24 16:56 ` Carlos Martín Nieto
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=20160212184023.GD19973@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=cmn@dwim.me \
--cc=git@vger.kernel.org \
/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 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 NNTP newsgroup(s).