All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Mehul Jain <mehul.jain2029@gmail.com>
Cc: git@vger.kernel.org, Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH v3 0/3] Introduce log.showSignature config variable
Date: Wed, 22 Jun 2016 13:31:46 -0700	[thread overview]
Message-ID: <xmqqr3bpklsd.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160622165126.12786-1-mehul.jain2029@gmail.com> (Mehul Jain's message of "Wed, 22 Jun 2016 22:21:23 +0530")

Mehul Jain <mehul.jain2029@gmail.com> writes:

> Add a new configuratation variable "log.showSignature" for git-log
> and related commands. "log.showSignature=true" will enable user to
> see GPG signature by default for git-log and related commands.
>
> Changes compared to v2:
> 	* A preparatory patch 1/3 has been introduced so that tests
> 	  in patches 2/3 and 3/3 can take advantage of it.

It is unclear how this change allows the remainder to "take
advanrage" to me.  Earlier, "signed" branch was created only when
the GPG prerequisite is met and with this change the branch is
always created, which is the only change as far as I can see.  But
the tests that are added in 2 and 3 are all protected with the GPG
prerequiste.

Besides, the invocation of "git commit -S" after this change is no
longer protected by the GPG prerequisite and it may even cause the
'setup' step to fail on a host without GPG.

What am I missing?  I do not quite see any reason to take 1/2; I
only see a possible downside without any upside.

The main two steps 2&3 looked good.

Thanks.

> 	* Mistake regarding branch in [patch v2 2/2] has been
> 	  corrected.
> 	* Tight coupling between the tests in [patch v2 2/2] has
> 	  been resovled.
>
> I would like to thanks Eric Sunshine for his feedback on previous
> series [1].



>
> [1]: http://thread.gmane.org/gmane.comp.version-control.git/297648 
>
> Mehul Jain (3):
>   t4202: refactoring of test
>   log: add "--no-show-signature" command line option
>   log: add log.showSignature configuration variable
>
>  Documentation/git-log.txt |  4 ++++
>  builtin/log.c             |  6 ++++++
>  revision.c                |  2 ++
>  t/t4202-log.sh            | 32 ++++++++++++++++++++++++++++++--
>  t/t7510-signed-commit.sh  |  7 +++++++
>  5 files changed, 49 insertions(+), 2 deletions(-)

  parent reply	other threads:[~2016-06-22 20:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 16:51 [PATCH v3 0/3] Introduce log.showSignature config variable Mehul Jain
2016-06-22 16:51 ` [PATCH v3 1/3] t4202: refactor test Mehul Jain
2016-06-24 14:12   ` Mehul Jain
2016-06-22 16:51 ` [PATCH v3 2/3] log: add "--no-show-signature" command line option Mehul Jain
2016-06-22 16:51 ` [PATCH v3 3/3] log: add log.showSignature configuration variable Mehul Jain
2016-06-22 20:31 ` Junio C Hamano [this message]
2016-06-23  5:44   ` [PATCH v3 0/3] Introduce log.showSignature config variable Mehul Jain
2016-06-23  6:32     ` Junio C Hamano
2016-06-24  9:21       ` Mehul Jain
2016-06-24 12:25         ` Eric Sunshine

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=xmqqr3bpklsd.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mehul.jain2029@gmail.com \
    --cc=sunshine@sunshineco.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 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.