From: Stefan Hajnoczi <stefanha@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
qemu-devel <qemu-devel@nongnu.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [RFC] Using gitlab for upstream qemu repo?
Date: Mon, 11 Jan 2021 09:57:47 +0000 [thread overview]
Message-ID: <20210111095747.GA43712@stefanha-x1.localdomain> (raw)
In-Reply-To: <CAFEAcA93iYHz2aXUY+sXwNqwNT3MD0HD6V+JoJJWt+xO9OUZNg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1579 bytes --]
On Tue, Jan 05, 2021 at 02:12:59PM +0000, Peter Maydell wrote:
> On Thu, 22 Oct 2020 at 17:48, Paolo Bonzini <pbonzini@redhat.com> wrote:
> > now that Gitlab is the primary CI infrastructure for QEMU, and that all
> > QEMU git repositories (including mirrors) are available on Gitlab, I
> > would like to propose that committers use Gitlab when merging commits to
> > QEMU repositories.
>
> > - right now Gitlab pulls from upstream repos and qemu.org pulls from
> > gitlab, but this is not true for the qemu, qemu-web and openbios
> > repositories where Gitlab pulls from qemu.org and qemu.org is the main
> > repository. With this switch, all the main repositories would be on
> > Gitlab and then mirrored to both qemu.org and GitHub. Having a
> > homogeneous configuration makes it easier to document what's going on.
>
> So IIRC we decided that we wanted to do this git.qemu.org -> gitlab
> switchover, but not during the 5.2 release. 5.2 is now out the door,
> so what's the next step to do the changeover? Now seems like a good
> time to do it so we can be happy we've dealt with any snags well
> before we get towards softfreeze.
Yes, let's do this now.
I will send a patch to point .gitmodules at GitLab. In the process of
doing this I noticed sgabios.git is not yet mirrored on GitLab. After I
create that repo (and any other missing repos) I will send a qemu.git
patch series that references the GitLab repos instead of qemu.org repos.
We can perform the mirroring direction switch that Paolo described above
independently.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-01-11 9:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 16:47 [RFC] Using gitlab for upstream qemu repo? Paolo Bonzini
2020-10-22 17:24 ` Eric Blake
2020-10-23 7:37 ` Gerd Hoffmann
2020-10-23 8:51 ` Daniel P. Berrangé
2020-10-23 13:41 ` Stefan Hajnoczi
2020-10-23 9:37 ` Paolo Bonzini
2020-10-23 8:44 ` Daniel P. Berrangé
2020-10-23 13:41 ` Stefan Hajnoczi
2020-10-26 11:04 ` Peter Maydell
2020-10-27 13:14 ` Michael Roth
2020-10-27 18:48 ` Paolo Bonzini
2020-10-27 14:08 ` Stefan Hajnoczi
2020-10-27 14:20 ` Daniel P. Berrangé
2020-10-27 14:32 ` Peter Maydell
2021-01-05 14:12 ` Peter Maydell
2021-01-11 9:57 ` Stefan Hajnoczi [this message]
2021-01-11 11:02 ` Paolo Bonzini
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=20210111095747.GA43712@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=edgar.iglesias@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).