All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Michael Roth" <mdroth@linux.vnet.ibm.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [RFC] Using gitlab for upstream qemu repo?
Date: Mon, 26 Oct 2020 11:04:06 +0000	[thread overview]
Message-ID: <CAFEAcA8OjeQ-utD56inorMk8dM6RNRzr-6Dv-YEW4n=qBi_MBQ@mail.gmail.com> (raw)
In-Reply-To: <672b8aa0-2128-23e1-b778-01a4d96b209d@redhat.com>

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.

> Nothing would change for developers, who would still have access to all
> three sets of repositories (git.qemu.org, gitlab.com and github.com).
> Committers however would need to have an account on the
> https://gitlab.com/qemu-project organization with access to the
> repositories they care about.  They would also lose write access to
> /srv/git on qemu.org.

Yes, this makes sense. Who in practice does it actually affect?
For the main qemu.git repo, my guess is just me, Michael Roth
for the stable branches, plus Richard H and Stefan H who both
volunteered to do a turn on the merge-handling rota once we
eventually get it set up to not depend on my ad-hoc CI setup.

I have a gitlab account so I'm set for this. Michael, do you
have an account there and are you OK with switching to doing
git pushes to the repo on gitlab rather than direct to qemu.org ?

thanks
-- PMM


  parent reply	other threads:[~2020-10-26 11:24 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 [this message]
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
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='CAFEAcA8OjeQ-utD56inorMk8dM6RNRzr-6Dv-YEW4n=qBi_MBQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=edgar.iglesias@gmail.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 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.