From: Peter Xu <peterx@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Claudio Fontana" <cfontana@suse.de>,
"Juan Quintela" <quintela@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Fabiano Rosas" <farosas@suse.de>,
"Steve Sistare" <steven.sistare@oracle.com>,
qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: migration maintenance, governance [Was: Re: [PATCH V4 0/2] migration file URI]
Date: Wed, 27 Sep 2023 11:15:35 -0400 [thread overview]
Message-ID: <ZRRHFyPC4wyyOUhx@x1n> (raw)
In-Reply-To: <ZRQ94J9vv83nLI4V@redhat.com>
On Wed, Sep 27, 2023 at 03:36:16PM +0100, Daniel P. Berrangé wrote:
> Even if not actively sending a PR, a possible starting point that could
> be done today, would be for someone to put up a gitlab.com branch that
> contains all the outstanding patch series that are considered ready
> to merge and validate a CI pipeline. That would both serve as a base for
> further work, and might be useful to Juan in assembling the next pull
> request.
Right.
Though that'll be slightly conter-productive if Juan already has a branch
that contains everything for a pull covering patches until two weeks ago.
I think before he left he has that on hand, maybe also tested a bit over
the branch. I actually talked to him on taking that branch over for this
time if he's busy, but unfortunately that conversation discontinued..
Having another branch has the risk that we'll have two base branches, if
Juan's branch will be sent out as the final pull next week and get merged.
But I do agree things need to be done if the pull doesn't come next week.
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2023-09-27 15:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 14:25 [PATCH V4 0/2] migration file URI Steve Sistare
2023-06-30 14:25 ` [PATCH V4 1/2] migration: " Steve Sistare
2023-08-30 13:16 ` Daniel P. Berrangé
2023-08-30 14:15 ` Steven Sistare
2023-09-08 10:52 ` Daniel P. Berrangé
2023-09-08 14:23 ` Steven Sistare
2023-06-30 14:25 ` [PATCH V4 2/2] migration: file URI offset Steve Sistare
2023-07-13 21:26 ` [PATCH V4 0/2] migration file URI Michael Galaxy
2023-08-22 12:00 ` Claudio Fontana
2023-08-22 13:25 ` Philippe Mathieu-Daudé
2023-08-30 13:09 ` Claudio Fontana
2023-09-13 13:00 ` Claudio Fontana
2023-09-27 13:14 ` migration maintenance, governance [Was: Re: [PATCH V4 0/2] migration file URI] Claudio Fontana
2023-09-27 13:56 ` Peter Xu
2023-09-27 14:36 ` Daniel P. Berrangé
2023-09-27 15:15 ` Peter Xu [this message]
2023-09-27 14:31 ` Daniel P. Berrangé
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=ZRRHFyPC4wyyOUhx@x1n \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=cfontana@suse.de \
--cc=farosas@suse.de \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=steven.sistare@oracle.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).