From: Tomi Ollila <tomi.ollila@iki.fi>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH 1/2] test: compute expected keyid from fingerprint
Date: Fri, 16 Sep 2022 19:42:14 +0300 [thread overview]
Message-ID: <y3bjq3a.ofcas0-too@iki.fi> (raw)
In-Reply-To: <87v8pso2uq.fsf@fifthhorseman.net>
On Mon, Sep 12 2022, Daniel Kahn Gillmor wrote:
> On Sun 2022-09-11 23:50:18 +0200, Justus Winter wrote:
>> Tomi Ollila <tomi.ollila@iki.fi> writes:
>>
>>> On Fri, Sep 09 2022, Justus Winter wrote:
>>>
>>>> ---
>>>> test/T350-crypto.sh | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/test/T350-crypto.sh b/test/T350-crypto.sh
>>>> index 3c6626b4..721cbfdd 100755
>>>> --- a/test/T350-crypto.sh
>>>> +++ b/test/T350-crypto.sh
>>>> @@ -467,7 +467,7 @@ expected='[[[{"id": "XXXXX",
>>>> "Date": "Sat, 01 Jan 2000 12:00:00 +0000"},
>>>> "body": [{"id": 1,
>>>> "sigstatus": [{"status": "error",
>>>> - "keyid": "6D92612D94E46381",
>>>> + "keyid": "'$(echo $FINGERPRINT | cut -c 25-)'",
>>>
>>> The "bashism" (works also in zsh) ${FINGERPRINT:24} works here
>>> (and has been used in other lines in this file
>>
>> Interesting. FTR, I saw this method being used elsewhere and simply
>> copied it. If that'd prevent merging the change, I'd actually prefer
>> introducing a variable KEYID that is set explicitly in the test library.
>> The reason for that is that in v5 OpenPGP, the keyid will be computed
>> differently.
>
> I don't think this should prevent merging the change -- Tomi is just
> offering an efficiency improvement.
Right, especially if it is consistent w/ code somewhere else.
(and it sure looks like: grep cut' ' test/* shows consistent usage)
Tomi
>
> i'd also be happy with the introduction of an explicitly-set KEYID
> variable. These could be distinct changes.
>
> --dkg
> _______________________________________________
> notmuch mailing list -- notmuch@notmuchmail.org
> To unsubscribe send an email to notmuch-leave@notmuchmail.org
prev parent reply other threads:[~2022-09-16 16:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 16:12 [PATCH 1/2] test: compute expected keyid from fingerprint Justus Winter
2022-09-09 16:13 ` [PATCH 2/2] test: replace aging OpenPGP key used in the test suite Justus Winter
2022-09-11 17:09 ` Daniel Kahn Gillmor
2022-09-20 1:27 ` David Bremner
2022-09-22 8:46 ` [PATCH] " Justus Winter
2022-09-22 10:01 ` Michael J Gruber
2022-09-22 10:14 ` Justus Winter
2022-09-22 10:21 ` Michael J Gruber
2022-09-23 15:49 ` Daniel Kahn Gillmor
2022-09-23 23:19 ` David Bremner
2022-09-11 17:20 ` [PATCH 1/2] test: compute expected keyid from fingerprint Tomi Ollila
2022-09-11 21:50 ` Justus Winter
2022-09-12 18:38 ` Daniel Kahn Gillmor
2022-09-16 16:42 ` Tomi Ollila [this message]
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=y3bjq3a.ofcas0-too@iki.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).