From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/crucible: update LICENSE information
Date: Mon, 8 Apr 2024 23:40:28 +0200 [thread overview]
Message-ID: <20240408234028.27f28acc@windsurf> (raw)
In-Reply-To: <20240404175552.672410-1-festevam@gmail.com>
On Thu, 4 Apr 2024 14:55:52 -0300
Fabio Estevam <festevam@gmail.com> wrote:
> Since crucible commit 7fe0bb96da65 ("move to BSD style license") the
> license has been changed to BSD-3.
>
> Change the license type and hash accordingly.
>
> Fixes:
> - http://autobuild.buildroot.net/results/14dfa0a47be54929c527c12fe9b95f34c1d8c7f5/
>
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
> ---
> package/crucible/crucible.hash | 2 +-
> package/crucible/crucible.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Thanks Fabio for the fix. The commit log was slightly not complete
enough, as it didn't say which Buildroot commit is being fixed by this
change. It is in fact your bump in commit
be3f95ed14559f8a9739a12cff604add622b0416 which forgot to update the
license. Having this information in the commit message is important as
it will allow us to understand to which of our stable branches this fix
should be backported.
So I've applied after adding this information in the commit message.
Thanks a lot!
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:[~2024-04-08 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 17:55 [Buildroot] [PATCH] package/crucible: update LICENSE information Fabio Estevam
2024-04-08 21:40 ` Thomas Petazzoni via buildroot [this message]
2024-05-06 11:22 ` 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=20240408234028.27f28acc@windsurf \
--to=buildroot@buildroot.org \
--cc=festevam@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