From: "Alex Bennée" <alex.bennee@linaro.org>
To: Tom Rini <trini@konsulko.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
u-boot@lists.denx.de, qemu-devel@nongnu.org
Subject: Re: [RFC PATCH] link principle license to COPYING
Date: Mon, 29 Sep 2025 19:08:41 +0100 [thread overview]
Message-ID: <87tt0ljfme.fsf@draig.linaro.org> (raw)
In-Reply-To: <20250929165042.GJ6093@bill-the-cat> (Tom Rini's message of "Mon, 29 Sep 2025 10:50:42 -0600")
Tom Rini <trini@konsulko.com> writes:
> On Mon, Sep 29, 2025 at 04:51:42PM +0100, Alex Bennée wrote:
>
>> Some license scanners are particularly dumb and when combined with
>> automatic license scanning for FLOSS accreditation on forges cause
>> problems on renewal. As GPL 2.0 applies to the core code link the main
>> licence text to COPYING to keep everything happy.
>>
>> This caused issues for the QEMU project recently as we mirror (two!)
>> copies of u-boot in our project.
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> Since Daniel Berrangé posted a similar patch 3 days ago, I assume the
> gitlab license renewal is coming up quickly.
We fixed it by temporally moving the repo to another project (although
it seems that is not a true mirror as mirroing needs the full paid
GitLab). However it broke a bunch of down-streams tracking earlier
branches.
>
> In principal, I'm fine with this and will apply a patch shortly.
>
> In practice, we've always had to get a human involved at Gitlab to get
> our license renewed as we're clearly within the required terms, it's
> just that we've also got some further reading people should do.
The GitLab process is a click though automated one now. However I did
check GitLab identifies the right license with the patch:
https://gitlab.com/stsquad/u-boot/
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2025-09-29 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 15:51 [RFC PATCH] link principle license to COPYING Alex Bennée
2025-09-29 16:50 ` Tom Rini
2025-09-29 18:08 ` Alex Bennée [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=87tt0ljfme.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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;
as well as URLs for NNTP newsgroup(s).