From: Peter Korsgaard <peter@korsgaard.com>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: Julien Olivain <ju.o@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/4] package/libgpg-error: bump version to 1.47
Date: Thu, 06 Jul 2023 10:44:38 +0200 [thread overview]
Message-ID: <877crd5szt.fsf@48ers.dk> (raw)
In-Reply-To: <87r0q9j9vy.fsf@48ers.dk> (Peter Korsgaard's message of "Sun, 18 Jun 2023 13:19:13 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:
>> Release notes:
>> https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgpg-error.git;a=blob;f=NEWS;h=9be1b714e05dbd7de7b822d9dbbd998f6bc26025;hb=a25cea92798a5ece3f49924911507f5335915ecc
>> Added upstream sha1 & sha256 hashes.
>> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> Committed, thanks.
Committed to 2023.02.x and 2023.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-06 8:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 18:52 [Buildroot] [PATCH 1/4] package/gnupg2: bump version to 2.4.2 Bernd Kuhls
2023-06-08 18:52 ` [Buildroot] [PATCH 2/4] package/libgcrypt: bump to version 1.10.2 Bernd Kuhls
2023-06-18 11:19 ` Peter Korsgaard
2023-07-06 8:43 ` Peter Korsgaard
2023-06-08 18:52 ` [Buildroot] [PATCH 3/4] package/libgpg-error: bump version to 1.47 Bernd Kuhls
2023-06-18 11:19 ` Peter Korsgaard
2023-07-06 8:44 ` Peter Korsgaard [this message]
2023-06-08 18:52 ` [Buildroot] [PATCH 4/4] package/libgpgme: bump to version 1.20.0 Bernd Kuhls
2023-06-18 11:19 ` Peter Korsgaard
2023-06-18 11:20 ` Peter Korsgaard
2023-06-18 11:19 ` [Buildroot] [PATCH 1/4] package/gnupg2: bump version to 2.4.2 Peter Korsgaard
2023-07-06 8:43 ` Peter Korsgaard
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=877crd5szt.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd.kuhls@t-online.de \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
/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