From: Peter Korsgaard <peter@korsgaard.com>
To: Baruch Siach via buildroot <buildroot@buildroot.org>
Cc: Paul Cercueil <paul@crapouillou.net>
Subject: Re: [Buildroot] [PATCH 1/1] package/strace: bump to version 6.3
Date: Sun, 04 Jun 2023 12:54:38 +0200 [thread overview]
Message-ID: <87ttvna45t.fsf@48ers.dk> (raw)
In-Reply-To: <87pm6xvwbm.fsf@tarshish> (Baruch Siach via buildroot's message of "Fri, 19 May 2023 06:19:03 +0300")
>>>>> "Baruch" == Baruch Siach via buildroot <buildroot@buildroot.org> writes:
> Hi Paul,
> On Thu, May 18 2023, Paul Cercueil wrote:
>> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>> ---
>> package/strace/strace.hash | 2 +-
>> package/strace/strace.mk | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/package/strace/strace.hash b/package/strace/strace.hash
>> index d49abf1f16..de2f8c52b9 100644
>> --- a/package/strace/strace.hash
>> +++ b/package/strace/strace.hash
>> @@ -1,5 +1,5 @@
>> # Locally calculated after checking signature with RSA key 0xA8041FA839E16E36
>> # https://strace.io/files/6.2/strace-6.2.tar.xz.asc
> This link needs update.
> I verified that the signature at
> https://strace.io/files/6.3/strace-6.3.tar.xz.asc matches the hash
> below.
Committed to next after fixing the link, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-06-04 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 21:06 [Buildroot] [PATCH 1/1] package/strace: bump to version 6.3 Paul Cercueil
2023-05-19 3:19 ` Baruch Siach via buildroot
2023-06-04 10:54 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-08 13:28 Konstantin Menyaev via buildroot
2023-06-08 13:41 ` Baruch Siach via buildroot
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=87ttvna45t.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=paul@crapouillou.net \
/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.