From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-gnupg: bump to version 0.4.9
Date: Sat, 23 Jul 2022 19:47:38 +0200 [thread overview]
Message-ID: <20220723194738.63e885ab@windsurf> (raw)
In-Reply-To: <20220621210529.251477-1-ju.o@free.fr>
On Tue, 21 Jun 2022 23:05:29 +0200
Julien Olivain <ju.o@free.fr> wrote:
> For change log, see:
> https://github.com/vsajip/python-gnupg/blob/0.4.9/README.rst#049
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> Tested with:
Applied to master, thanks. However, you had forgotten to run "make
legal-info", and the license file had changed, causing its hash to no
longer be valid.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-07-23 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 21:05 [Buildroot] [PATCH 1/1] package/python-gnupg: bump to version 0.4.9 Julien Olivain
2022-07-23 17:47 ` Thomas Petazzoni via buildroot [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220723194738.63e885ab@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox