From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, Alex <agrambot@gmail.com>,
Ramsay Jones <ramsay@ramsayjones.plus.com>
Subject: Re: [PATCH v2] gpg-interface: use more status letters
Date: Wed, 28 Sep 2016 12:59:27 -0700 [thread overview]
Message-ID: <xmqqshsjiyn4.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <c4777ef68059034d7ad4697a06bba3cabbdc9265.1475053649.git.git@drmicha.warpmail.net> (Michael J. Gruber's message of "Wed, 28 Sep 2016 16:24:13 +0200")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> - Use GNUPGHOME="$HOME/gnupg-home-not-used" just like in other tests (lib).
If you are not using /dev/null, I expected you to do
. ./test-lib.sh
GNUPGHOME_saved=$GNPGHOME
. "$TEST_DIRECTORY/lib-gpg.sh"
and then use
GNUPGHOME="$GNUPGHOME_saved" git log -1 ...
in the test.
Otherwise, you are not futureproofing your use and only adding to
maintenance burden. The gnupg-home-not-used hack may turn out to be
a problematic and test-lib.sh may update to point to somewhere else,
which will leave your copy still pointing at the old problematic
place).
> - Do not parse for signer UID in the ERRSIG case (and test that we do not).
Good.
> - Retreat "rather" addition from the doc: good/valid are terms that we use
> differently from gpg anyways.
OK.
> + "X" for a good expired signature, or good signature made by an expired key,
As an attempt to clarify that we cover both EXPSIG and EXPKEYSIG
cases, I think this is good enough. I may have phrased the former
slightly differently, though: "a good signature that has expired".
I have no strong opinion if we want to stress that we cover both
cases, though, which is I think what Ramsay's comment was about.
Thanks.
next prev parent reply other threads:[~2016-09-28 19:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 6:05 Request: Extra case for %G? format Alex
2016-09-26 11:53 ` Michael J Gruber
2016-09-26 17:18 ` Alex
2016-09-27 14:31 ` [PATCH] gpg-interface: use more status letters Michael J Gruber
2016-09-27 17:25 ` Junio C Hamano
2016-09-28 14:24 ` [PATCH v2] " Michael J Gruber
2016-09-28 15:10 ` Ramsay Jones
2016-09-28 19:59 ` Junio C Hamano [this message]
2016-09-28 21:09 ` Ramsay Jones
2016-09-30 9:41 ` Michael J Gruber
2016-09-30 16:16 ` Junio C Hamano
2016-10-06 21:43 ` Junio C Hamano
2016-10-10 12:59 ` Michael J Gruber
2016-10-10 17:58 ` Junio C Hamano
2016-10-12 13:04 ` [PATCH v3] " Michael J Gruber
2016-09-30 9:33 ` [PATCH v2] " Michael J Gruber
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=xmqqshsjiyn4.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=agrambot@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.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.