From: Santiago Torres <santiago@nyu.edu>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Subject: Re: [PATCH v4 2/6] t/t7030-verify-tag.sh: Adds validation for multiple tags
Date: Mon, 4 Apr 2016 21:46:10 -0400 [thread overview]
Message-ID: <20160405014609.GB12006@LykOS> (raw)
In-Reply-To: <CAPig+cQJ6EzJ0976NJBHXRZyuTf1dr+0ZOvzrCfiTVZOp6fXBA@mail.gmail.com>
>
> The bulk of this description is merely repeating what the patch itself
> already says, thus is redundant. The entire commit message could
> probably be collapsed to:
>
> t7030: test verify-tag with multiple tags
>
> git-verify-tag accepts multiple tags as arguments, however,
> existing tests only ever invoke it with a single tag, so add a
> test invoking it with multiple tags.
Yeah, this is actually clearer. Sorry for the academ-ose commit message.
> > +test_expect_success GPG 'verify multiple tags' '
> > + tags="fourth-signed sixth-signed seventh-signed" &&
> > + for i in $tags; do
> > + git verify-tag -v --raw $i || return 1
> > + done >expect.stdout 2>expect.stderr.1 &&
> > + grep GOODSIG <expect.stderr.1 >expect.stderr &&
> > + git verify-tag -v --raw $tags >actual.stdout 2>actual.stderr.1 &&
> > + grep GOODSIG <actual.stderr.1 >actual.stderr &&
>
> Hmm, I had expected you to adopt Peff's suggestion[1] for the greps:
>
> grep '^.GNUPG:.' ...
>
> [1]: http://article.gmane.org/gmane.comp.version-control.git/290691
I thought this was an stylistic thing. I can of course adopt this
suggestion.
Thanks,
-Santiago
next prev parent reply other threads:[~2016-04-05 1:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 22:22 [PATCH v4 0/6] tag: move PGP verification code to tag.c santiago
2016-04-04 22:22 ` [PATCH v4 1/6] builtin/verify-tag.c: Ignore SIGPIPE on gpg-interface santiago
2016-04-04 22:22 ` [PATCH v4 2/6] t/t7030-verify-tag.sh: Adds validation for multiple tags santiago
2016-04-05 1:27 ` Eric Sunshine
2016-04-05 1:46 ` Santiago Torres [this message]
2016-04-05 3:51 ` Eric Sunshine
2016-04-04 22:22 ` [PATCH v4 3/6] builtin/verify-tag: move verification code to tag.c santiago
2016-04-04 22:22 ` [PATCH v4 4/6] tag.c: Replace varialbe name for readability santiago
2016-04-05 1:30 ` Eric Sunshine
2016-04-04 22:22 ` [PATCH v4 5/6] tag: use pgp_verify_function in tag -v call santiago
2016-04-05 1:39 ` Eric Sunshine
2016-04-05 1:43 ` Santiago Torres
2016-04-04 22:22 ` [PATCH v4 6/6] tag.c: Change gpg_verify_tag argument to sha1 santiago
2016-04-05 2:00 ` Eric Sunshine
2016-04-05 2:10 ` Santiago Torres
2016-04-05 3:46 ` 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=20160405014609.GB12006@LykOS \
--to=santiago@nyu.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--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 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).