From: Jeff King <peff@peff.net>
To: Mehul Jain <mehul.jain2029@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Austin English <austinenglish@gmail.com>
Subject: Re: [RFC/PATCH 2/2] log: add "--no-show-signature" command line option
Date: Fri, 27 May 2016 13:48:08 -0400 [thread overview]
Message-ID: <20160527174807.GA1614@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqq4m9js8qb.fsf@gitster.mtv.corp.google.com>
On Fri, May 27, 2016 at 10:37:16AM -0700, Junio C Hamano wrote:
> Mehul Jain <mehul.jain2029@gmail.com> writes:
>
> > On Thu, May 26, 2016 at 10:52 PM, Junio C Hamano <gitster@pobox.com> wrote:
> >
> >> The only reason why teaching the "--no-show-signature" option to
> >> these commands is a good idea is because it would help people who
> >> create an alias with "--show-sig" in early part of the command line,
> >> e.g.
> >>
> >> [alias] fp = format-patch --show-signature
> >>
> >> by allowing them to countermand with --no-show-signature, i.e.
> >>
> >> $ git fp --no-show-signature ...
> >> ...
> >
> > Just out of curiosity, I was thinking that we might be able to teach
> > "--no-show-signature" option only to git-show, git-log, git-whatchanged
> > and git-reflog.
>
> Yeah, I know it is possible with extra code, but I do not think of a
> good reason why it is necessary.
Not only "not necessary" but "actively worse" in my opinion. We have
--show-signature in revision.c, and that is reason enough to have
--no-show-signature, in case anybody would want to countermand an
earlier request (whether from config that is soon to exist, or from a
previous --show-signature on the command line), or just because somebody
feels like making sure git is doing what they want without bothering to
check the defaults.
We add the "--no-" form by default for all of our bools parsed by
parse-options. The only reason it is not already here is that this
option parsing predates our use of parse-options, and nobody had
bothered to go back and add it. But doing so is a win simply for
consistency if nothing else, IMHO.
I actually think it would be nice to convert all of handle_revision_opt
to parse-options, but that's a non-trivial task. And I certainly
wouldn't want it to hold up this otherwise simple topic.
-Peff
next prev parent reply other threads:[~2016-05-27 17:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 13:06 [RFC/PATCH 0/2] Introduce "log.showSignature" config variable Mehul Jain
2016-05-26 13:06 ` [RFC/PATCH 1/2] log: add "log.showsignature" configuration variable Mehul Jain
2016-05-26 13:42 ` Remi Galan Alfonso
2016-05-26 15:04 ` Mehul Jain
2016-05-26 15:43 ` Remi Galan Alfonso
2016-05-26 16:06 ` Mehul Jain
2016-05-27 4:01 ` Pranit Bauva
2016-05-26 16:59 ` Jeff King
2016-05-27 6:04 ` Mehul Jain
2016-05-26 13:06 ` [RFC/PATCH 2/2] log: add "--no-show-signature" command line option Mehul Jain
2016-05-26 16:32 ` Jeff King
2016-05-26 16:42 ` Mehul Jain
2016-05-26 17:01 ` Jeff King
2016-05-26 17:22 ` Junio C Hamano
2016-05-27 6:08 ` Mehul Jain
2016-05-27 17:37 ` Junio C Hamano
2016-05-27 17:48 ` Jeff King [this message]
2016-05-27 2:55 ` [RFC/PATCH 0/2] Introduce "log.showSignature" config variable Austin English
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=20160527174807.GA1614@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=austinenglish@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mehul.jain2029@gmail.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 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).