From: "Shawn O. Pearce" <spearce@spearce.org>
To: SZEDER G??bor <szeder@ira.uka.de>, Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] bash: don't offer remote transport helpers as subcommands
Date: Thu, 28 Jan 2010 07:19:51 -0800 [thread overview]
Message-ID: <20100128151951.GB20185@spearce.org> (raw)
In-Reply-To: <1264157691-27187-1-git-send-email-szeder@ira.uka.de>
SZEDER G??bor <szeder@ira.uka.de> wrote:
> Since commits a2d725b7 (Use an external program to implement fetching
> with curl, 2009-08-05) and c9e388bb (Make the
> "traditionally-supported" URLs a special case, 2009-09-03) remote
> transport helpers like 'remote-ftp' and 'remote-curl' are offered by the
> completion script as available subcommands. Not good, since they are
> helpers, therefore should not be offered, so filter them out.
>
> Signed-off-by: SZEDER G??bor <szeder@ira.uka.de>
> ---
>
> Maybe maint-worthy? 1.6.5 was the first release with this bug, but
> nobody complained since then.
Yup, should be in maint.
Acked-by: Shawn O. Pearce <spearce@spearce.org>
> contrib/completion/git-completion.bash | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> index 9651720..7def62c 100755
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -568,6 +568,7 @@ __git_list_porcelain_commands ()
> read-tree) : plumbing;;
> receive-pack) : plumbing;;
> reflog) : plumbing;;
> + remote-*) : transport;;
> repo-config) : deprecated;;
> rerere) : plumbing;;
> rev-list) : plumbing;;
> --
> 1.6.6.1.361.gc5121
--
Shawn.
prev parent reply other threads:[~2010-01-28 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 10:54 [PATCH] bash: don't offer remote transport helpers as subcommands SZEDER Gábor
2010-01-28 15:19 ` Shawn O. Pearce [this message]
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=20100128151951.GB20185@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder@ira.uka.de \
/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).