From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Mehul Jain <mehul.jain2029@gmail.com>,
git@vger.kernel.org, Austin English <austinenglish@gmail.com>
Subject: Re: [RFC/PATCH 2/2] log: add "--no-show-signature" command line option
Date: Thu, 26 May 2016 10:22:01 -0700 [thread overview]
Message-ID: <xmqqiny0wx8m.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160526163241.GC18210@sigill.intra.peff.net> (Jeff King's message of "Thu, 26 May 2016 12:32:42 -0400")
Jeff King <peff@peff.net> writes:
> On Thu, May 26, 2016 at 06:36:47PM +0530, Mehul Jain wrote:
>
>> If "log.showsignature=true", then there is no way to override it using
>> command line switch.
>>
>> Teach "git log" and "git show" about "--no-show-signature" command line
>> option.
>
> I think this is teaching all of the revision machinery about it (which
> is a good thing).
I agree that the proposed commit log message should be updated to
say so.
Because we do not want .showsignature configuration to affect
rev-list nor format-patch, and we will not make "--show-sig" the
default for them either. From that point of view, there is no
reason for them to know about the "--no-show-signature" option.
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 ...
If we are updating the log message in the final submission of this
patch, we'd want it to be clear that the presence of this option is
not an excuse to introduce .showsignature that affects rev-list
later to make sure we do not have to waste our time rejecting such a
patch in the future.
next prev parent reply other threads:[~2016-05-26 17:22 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 [this message]
2016-05-27 6:08 ` Mehul Jain
2016-05-27 17:37 ` Junio C Hamano
2016-05-27 17:48 ` Jeff King
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=xmqqiny0wx8m.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=austinenglish@gmail.com \
--cc=git@vger.kernel.org \
--cc=mehul.jain2029@gmail.com \
--cc=peff@peff.net \
/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.