From: Paolo Bonzini <pbonzini@redhat.com>
To: "Eric Blake" <eblake@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [RFC] Using gitlab for upstream qemu repo?
Date: Fri, 23 Oct 2020 11:37:39 +0200 [thread overview]
Message-ID: <b8090f8a-1592-0959-7bd7-0c5b18a13f11@redhat.com> (raw)
In-Reply-To: <9f6c63c6-599b-ac15-42e2-b9c1991fc7ee@redhat.com>
On 22/10/20 19:24, Eric Blake wrote:
> Does this proposal mean that pull requests would have to switch to
> gitlab merge requests, or would there be a transition period where
> submaintainers still send pull requests via whichever means desired
> (mail or gitlab merge request), but the eventual committer repackages
> that as a gitlab merge request before it is upstream?
No, all it means is that Peter would have to do "git push gitlab"
instead of "git push origin" :) and likewise for qemu-web and openbios.
I'm open to switching (later) to merge requests for qemu-web, but that's
a different story.
Paolo
next prev parent reply other threads:[~2020-10-23 9:38 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 [this message]
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
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=b8090f8a-1592-0959-7bd7-0c5b18a13f11@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=eblake@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--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).