From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/fwts: bump version to 23.07.00
Date: Sun, 9 Jul 2023 18:29:42 +0200 [thread overview]
Message-ID: <20230709182942.2ef996fd@windsurf> (raw)
In-Reply-To: <20230709095058.1547133-2-bernd@kuhls.net>
On Sun, 9 Jul 2023 11:50:58 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> Release notes:
> https://wiki.ubuntu.com/FirmwareTestSuite/ReleaseNotes
>
> Updated license hash due to copyright year bump and formatting changes:
> https://git.launchpad.net/fwts/commit/debian/copyright?id=64d2ea181d887d877104cd08defbd3427015070a
> https://git.launchpad.net/fwts/commit/debian/copyright?id=88edd4da5885e182a339c57c4d70768f6fab695b
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> package/fwts/fwts.hash | 4 ++--
> package/fwts/fwts.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
Applied to master, thanks.
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
next prev parent reply other threads:[~2023-07-09 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 9:50 [Buildroot] [PATCH 1/2] package/fwts: Fix build with BR2_OPTIMIZE_0 Bernd Kuhls
2023-07-09 9:50 ` [Buildroot] [PATCH 2/2] package/fwts: bump version to 23.07.00 Bernd Kuhls
2023-07-09 16:29 ` Thomas Petazzoni via buildroot [this message]
2023-07-09 16:29 ` [Buildroot] [PATCH 1/2] package/fwts: Fix build with BR2_OPTIMIZE_0 Thomas Petazzoni via buildroot
[not found] ` <20230709182938.00cef6ca__21548.8254021452$1688920206$gmane$org@windsurf>
2023-07-09 16:42 ` Bernd Kuhls
2023-07-09 16:46 ` Thomas Petazzoni via buildroot
2023-07-17 13:02 ` 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=20230709182942.2ef996fd@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--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