From: "Michael S. Tsirkin" <mst@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
Kevin OConnor <kevin@koconnor.net>,
Gerd Hoffmann <kraxel@redhat.com>,
Marcel Apfelbaum <marcel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] Delaying -rc0?
Date: Wed, 4 Mar 2015 18:20:55 +0100 [thread overview]
Message-ID: <20150304172055.GA7092@redhat.com> (raw)
In-Reply-To: <87fv9ku2sa.fsf@blackfin.pond.sub.org>
On Wed, Mar 04, 2015 at 05:48:37PM +0100, Markus Armbruster wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
>
> > On Wed, Mar 04, 2015 at 12:14:21AM +0900, Peter Maydell wrote:
> >> On 4 March 2015 at 00:07, Marcel Apfelbaum <marcel@redhat.com> wrote:
> >> > In the mean time this series depends on Igor's ACPI dynamic series that took
> >> > a lot of time to review and even Michael's PULL request with it is not yet
> >> > in master.
> >>
> >> You can view this as an argument against enormous pull requests
> >> with nearly a hundred patches in them -- they're much more likely
> >> to hit multiple issues in submission with minor things that need
> >> fixing, simply because of their size...
> >>
> >> thanks
> >> -- PMM
> >
> > Right. There were acpi changes by Igor and PCI changes by Markus,
>
> The latter is my "[PATCH 00/10] pci: Partial conversion to realize".
> Quite a few pending series depend on it.
>
> > trying to merge them at once is what created this.
> > I guess I could instead just do two unrelated pull requests
> > that can be merged in parallel. Though in Marcel's case, the
> > problems were all in Igor's patches and these are exactly
> > the ones Marcel's code depends on.
>
> If we can decouple the two, problems with one won't hold up the other
> anymore.
>
> I can do a pull request for just my series, if that helps.
I think it's not necessary at this point.
> But I'm
> prepared to leave that coveted, glamorous and rewarding job to you ;)
next prev parent reply other threads:[~2015-03-04 17:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 12:33 [Qemu-devel] Delaying -rc0? Paolo Bonzini
2015-03-02 12:44 ` Peter Maydell
2015-03-02 13:11 ` Paolo Bonzini
2015-03-03 13:12 ` Marcel Apfelbaum
2015-03-03 13:57 ` Paolo Bonzini
2015-03-03 14:57 ` Gerd Hoffmann
2015-03-03 15:07 ` Marcel Apfelbaum
2015-03-03 15:14 ` Peter Maydell
2015-03-04 7:27 ` Markus Armbruster
2015-03-04 12:13 ` Gerd Hoffmann
2015-03-04 12:19 ` Michael S. Tsirkin
2015-03-04 12:26 ` Michael S. Tsirkin
2015-03-04 16:48 ` Markus Armbruster
2015-03-04 17:20 ` Michael S. Tsirkin [this message]
2015-03-04 12:08 ` Gerd Hoffmann
2015-03-02 21:42 ` Stefan Hajnoczi
2015-03-03 13:37 ` Michael S. Tsirkin
2015-03-04 7:27 ` Markus Armbruster
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=20150304172055.GA7092@redhat.com \
--to=mst@redhat.com \
--cc=armbru@redhat.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=marcel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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.