From: Tomi Ollila <tomi.ollila@iki.fi>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] test: avoid unnecessary extraction of the test fingerprint
Date: Wed, 08 May 2019 18:55:43 +0300 [thread overview]
Message-ID: <m2lfzh3pq8.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <20190507130135.14898-1-dkg@fifthhorseman.net>
On Tue, May 07 2019, Daniel Kahn Gillmor wrote:
> FINGERPRINT is already exported by add_gnupg_home, so this is
> unnecessary. This change also happens to get rid of the superfluous
> check-trustdb spew from the test suite that looked like this:
>
> gpg: checking the trustdb
> gpg: marginals needed: 3 completes needed: 1 trust model: pgp
> gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
>
> Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
LGTM (just quick glance -- but code removal is always good thing when
possible ! ;)
(I trust dkg knows what he is doing in this matter)
Tomi
> ---
> test/T357-index-decryption.sh | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/test/T357-index-decryption.sh b/test/T357-index-decryption.sh
> index c9cd5e30..8a2d4c02 100755
> --- a/test/T357-index-decryption.sh
> +++ b/test/T357-index-decryption.sh
> @@ -8,8 +8,6 @@ test_description='indexing decrypted mail'
> ##################################################
>
> add_gnupg_home
> -# get key fingerprint
> -FINGERPRINT=$(gpg --no-tty --list-secret-keys --with-colons --fingerprint | grep '^fpr:' | cut -d: -f10)
>
> # create a test encrypted message
> test_begin_subtest 'emacs delivery of encrypted message'
> --
> 2.20.1
next prev parent reply other threads:[~2019-05-08 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 13:01 [PATCH] test: avoid unnecessary extraction of the test fingerprint Daniel Kahn Gillmor
2019-05-08 15:55 ` Tomi Ollila [this message]
2019-05-10 10:16 ` David Bremner
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: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2lfzh3pq8.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=dkg@fifthhorseman.net \
--cc=notmuch@notmuchmail.org \
/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://yhetil.org/notmuch.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).