From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org,
Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: [PATCH] .gitmodules: move u-boot mirrors to qemu-project-mirrors
Date: Mon, 15 Sep 2025 14:20:01 +0100 [thread overview]
Message-ID: <87segnq2da.fsf@draig.linaro.org> (raw)
In-Reply-To: <aMgD83wAjZMurYnI@redhat.com> ("Daniel P. Berrangé"'s message of "Mon, 15 Sep 2025 13:17:55 +0100")
Daniel P. Berrangé <berrange@redhat.com> writes:
> On Mon, Sep 08, 2025 at 03:19:11PM +0100, Alex Bennée wrote:
>> To continue our GitLab Open Source Program license we need to pass an
>> automated license check for all repos under qemu-project. While U-Boot
>> is clearly GPLv2 rather than fight with the automated validation
>> script just move the mirror across to a separate project.
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> Suggested-by: Daniel P. Berrangé <berrange@redhat.com>
>> Cc: qemu-stable@nongnu.org
>> ---
>> .gitmodules | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/.gitmodules b/.gitmodules
>> index 73cae4cd4da..e27dfe8c2c1 100644
>> --- a/.gitmodules
>> +++ b/.gitmodules
>> @@ -15,7 +15,7 @@
>> url = https://gitlab.com/qemu-project/qemu-palcode.git
>> [submodule "roms/u-boot"]
>> path = roms/u-boot
>> - url = https://gitlab.com/qemu-project/u-boot.git
>> + url = https://gitlab.com/qemu-project-mirrors/u-boot.git
>> [submodule "roms/skiboot"]
>> path = roms/skiboot
>> url = https://gitlab.com/qemu-project/skiboot.git
>> @@ -27,7 +27,7 @@
>> url = https://gitlab.com/qemu-project/seabios-hppa.git
>> [submodule "roms/u-boot-sam460ex"]
>> path = roms/u-boot-sam460ex
>> - url = https://gitlab.com/qemu-project/u-boot-sam460ex.git
>> + url = https://gitlab.com/qemu-project-mirrors/u-boot-sam460ex.git
>> [submodule "roms/edk2"]
>> path = roms/edk2
>> url = https://gitlab.com/qemu-project/edk2.git
>
> Are these the only 2 repos that are still blocking the OSS program
> approval checks we need ?
There are two biosbits repos and the s390 tools as well, see:
https://gitlab.com/qemu-project-mirrors
but we don't reference them as submodules.
>
> This is pretty ugly, but unless upstream u-boot is willing to add a COPYING
> file very quickly, I'm not seeing better options, given that GitLab's OSS
> Program approval is driven off entirely automated processing of the
> COPYING/LICENSE file contents.
>
> If upstream u-boot.git added a good COPYING file, we would have to handle
> the u-boot-sam460ex fork by pulling all of u-boot.git modern histry into
> u-boot-sam460ex.git and ensuring the primary branch was master so GitLab
> sees the COPYING file. The QEMU sub-module would still point to the
> original old commit with the sam640ex changes we need, lacking a COPYING
> file but that won't be a problem.
>
>
> My only comment is that if we go down the route of this patch, I think we
> should aim to move all read-only mirrored 3rd party stuff under the new
> /qemu-project-mirrors group, so that /qemu is exclusively for code which
> we actively maintain ourselves (and thus have control over licensing)
Sure - I just wanted the minimum to get over the renewal.
However I can't hit the button now, something is stopping me and its not
entirely clear. I think maybe we need a Tax ID.
> Every single active stable branch will need this change too, otherwise
> they'll be unable to find the submodules we moved.
Once this is in it will be easy enough to apply to the stable branches.
>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
>
> With regards,
> Daniel
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-09-15 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 14:19 [PATCH] .gitmodules: move u-boot mirrors to qemu-project-mirrors Alex Bennée
2025-09-13 10:41 ` Alex Bennée
2025-09-15 12:17 ` Daniel P. Berrangé
2025-09-15 13:20 ` Alex Bennée [this message]
2025-09-26 9:27 ` Christoph Müllner
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=87segnq2da.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.