From: Mehul Jain <mehul.jain2029@gmail.com>
To: git@vger.kernel.org
Cc: Eric Sunshine <sunshine@sunshineco.com>,
Mehul Jain <mehul.jain2029@gmail.com>
Subject: [PATCH v3 0/3] Introduce log.showSignature config variable
Date: Wed, 22 Jun 2016 22:21:23 +0530 [thread overview]
Message-ID: <20160622165126.12786-1-mehul.jain2029@gmail.com> (raw)
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.
* 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(-)
--
2.9.0.rc0.dirty
next reply other threads:[~2016-06-22 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 16:51 Mehul Jain [this message]
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 ` [PATCH v3 0/3] Introduce log.showSignature config variable Junio C Hamano
2016-06-23 5:44 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160622165126.12786-1-mehul.jain2029@gmail.com \
--to=mehul.jain2029@gmail.com \
--cc=git@vger.kernel.org \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).