From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Fabio Estevam <festevam@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/crucible: fix license
Date: Fri, 10 May 2024 23:02:02 +0200 [thread overview]
Message-ID: <20240510230202.5da6375e@windsurf> (raw)
In-Reply-To: <20240307171610.47962-1-fontaine.fabrice@gmail.com>
On Thu, 7 Mar 2024 18:16:10 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> crucible is licensed under BSD-3-Clause since bump to version 2023.11.02
> in commit be3f95ed14559f8a9739a12cff604add622b0416 and
> https://github.com/usbarmory/crucible/commit/7fe0bb96da655b4e83031a99115d37f88a171e9f
>
> Fixes: be3f95ed14559f8a9739a12cff604add622b0416
> - http://autobuild.buildroot.org/results/6183b11f1564bc07adfff2b02cb0607d0b1de54e
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/crucible/crucible.hash | 2 +-
> package/crucible/crucible.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Sorry, I'm only noticing this patch now, and this has already been
fixed by a different patch from Fabio, in commit
9f4cae383a061b52424bf37900aaa221e3a2f3c5. Sorry about that: your patch
came in earlier, so it should have been the one that got applied.
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:[~2024-05-10 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 17:16 [Buildroot] [PATCH 1/1] package/crucible: fix license Fabrice Fontaine
2024-03-07 20:38 ` Fabio Estevam
2024-05-10 21:02 ` 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=20240510230202.5da6375e@windsurf \
--to=buildroot@buildroot.org \
--cc=festevam@gmail.com \
--cc=fontaine.fabrice@gmail.com \
--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