From: Jeff King <peff@peff.net>
To: Mehul Jain <mehul.jain2029@gmail.com>
Cc: 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: Thu, 26 May 2016 13:01:07 -0400 [thread overview]
Message-ID: <20160526170107.GA20677@sigill.intra.peff.net> (raw)
In-Reply-To: <CA+DCAeRRunqgbbbpDDK6gA-cXYrPtkmAuX-ERvtDtXsD2Z=xkw@mail.gmail.com>
On Thu, May 26, 2016 at 10:12:30PM +0530, Mehul Jain wrote:
> On Thu, May 26, 2016 at 10:02 PM, Jeff King <peff@peff.net> wrote:
> > On Thu, May 26, 2016 at 06:36:47PM +0530, Mehul Jain wrote:
> >> diff --git a/t/t4202-log.sh b/t/t4202-log.sh
> >> index 36be9a1..ea24259 100755
> >> --- a/t/t4202-log.sh
> >> +++ b/t/t4202-log.sh
> >> @@ -901,6 +901,13 @@ test_expect_success GPG 'log.showsignature=true behaves like --show-signature' '
> >> test_i18ngrep "gpg: Good signature" actual
> >> '
> >>
> >> +test_expect_success GPG '--no-show-signature overrides log.showsignature=true' '
> >> + git config log.showsignature true &&
> >> + git log -1 --no-show-signature signed >actual &&
> >> + test "$(test_i18ngrep "gpg: Signature made" actual)" = "" &&
> >> + test "$(test_i18ngrep "gpg: Good signature" actual)" = ""
> >> +'
> >
> > Perhaps it would be more robust to simply grep for "gpg:". We should not
> > be seeing any gpg-related lines in the output. It probably isn't that
> > big a deal in practice, though. If the output from gpg changes, this
> > test could report a false success, but all of the other nearby tests
> > would show a breakage, so somebody would probably notice.
>
> That's a very good point. I will make the changes accordingly.
While you are here, note that test_i18ngrep can already do the
"negative" grep, like:
test_i18ngrep ! "^gpg:" actual
Though see my comments in the other part of the thread; I'm not sure
it's worth using i18ngrep at all.
-Peff
next prev parent reply other threads:[~2016-05-26 17:01 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 [this message]
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
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=20160526170107.GA20677@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=austinenglish@gmail.com \
--cc=git@vger.kernel.org \
--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).