From: John Keeping <john@keeping.me.uk>
To: "SZEDER Gábor" <szeder@ira.uka.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] completion: verify-tag is not plumbing
Date: Mon, 1 Feb 2016 10:44:11 +0000 [thread overview]
Message-ID: <20160201104411.GD29880@serenity.lan> (raw)
In-Reply-To: <20160131143759.Horde.Ylcq6ydVoLduXCzBPzVjZMh@webmail.informatik.kit.edu>
On Sun, Jan 31, 2016 at 02:37:59PM +0100, SZEDER Gábor wrote:
>
> Quoting John Keeping <john@keeping.me.uk>:
>
> > According to command-list.txt, verify-tag is an ancillary interrogator,
> > which means that it should be completed by "git verify-<TAB>" in the
> > same way as verify-commit.
> >
> > Remove it from the list of plumbing commands so that it is treated as
> > porcelain and completed.
>
> I'm not sure. There are commands among the ancillary interrogators
> that are basically porcelains (e.g. blame), while some are more like
> plumbing (e.g. rerere, rev-parse). In general the completion script
> supports the former but not the latter commands.
>
> Now, the real porcelain-ish way to verify a tag is via 'git tag
> -v|--verify', and according to a925c6f165a3 (bash: Classify more
> commends out of completion., 2007-02-04), the commit removing
> verify-tag from the completed commands, verify-tag was kept around for
> backwards compatibility reasons. OTOH verify-commit was introduced in
> d07b00b7f31d (verify-commit: scriptable commit signature verification,
> 2014-06-23), and as the subject line states it was intended more as a
> plumbing command.
>
> So I think we should keep excluding verify-tag from the list of
> porcelain commands in the completion script, and it was an oversight
> not to exclude verify-commit as well when it was introduced.
I can accept that argument about verify-commit and verify-tag, but
listing verify-tag as plumbing is incorrect according to
command-list.txt (and thus git(1)). If we're going to classify
commands, shouldn't we be consistent in how we do so?
> > Signed-off-by: John Keeping <john@keeping.me.uk>
> > ---
> > contrib/completion/git-completion.bash | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/contrib/completion/git-completion.bash
> > b/contrib/completion/git-completion.bash
> > index 51f5223..250788a 100644
> > --- a/contrib/completion/git-completion.bash
> > +++ b/contrib/completion/git-completion.bash
> > @@ -728,7 +728,6 @@ __git_list_porcelain_commands ()
> > write-tree) : plumbing;;
> > var) : infrequent;;
> > verify-pack) : infrequent;;
> > - verify-tag) : plumbing;;
> > *) echo $i;;
> > esac
> > done
> > --
> > 2.7.0
next prev parent reply other threads:[~2016-02-01 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 12:44 [PATCH] completion: verify-tag is not plumbing John Keeping
2016-01-31 13:37 ` SZEDER Gábor
2016-02-01 10:44 ` John Keeping [this message]
2016-02-01 18:51 ` Junio C Hamano
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=20160201104411.GD29880@serenity.lan \
--to=john@keeping.me.uk \
--cc=git@vger.kernel.org \
--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 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.