All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>,
	Alexander Graf <agraf@suse.de>,
	Anthony Liguori <aliguori@amazon.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/2] Use g_new() & friends where that makes obvious sense
Date: Mon, 03 Feb 2014 09:40:03 +0100	[thread overview]
Message-ID: <87eh3kfv30.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <CAFEAcA_vwqdzH2BsKuPL038qMk4n-=mNx1MWK0R6yT3qXcaeiQ@mail.gmail.com> (Peter Maydell's message of "Fri, 31 Jan 2014 16:13:16 +0000")

Peter Maydell <peter.maydell@linaro.org> writes:

> On 31 January 2014 15:53, Markus Armbruster <armbru@redhat.com> wrote:
>> PATCH 1/2 fixes a bug found by compiling the original PATCH 2/2.
>> Evidence for my claim that PATCH 2/2 lets the compiler catch more type
>> errors :)
>>
>> Markus Armbruster (2):
>>   qga: Fix memory allocation pasto
>>   Use g_new() & friends where that makes obvious sense
>
>>  186 files changed, 376 insertions(+), 415 deletions(-)
>
> No objection in principle, but I think this is going to be
> hideous merge pain since it touches a huge range of files.
> Could you split it up into separate patches that could
> reasonably go in via the appropriate submaintainer trees?

No merge pain at all if you simply rerun the included Coccinelle patch!

Splitting the patch may shift some pain from the choke point (you) to
submaintainers and me.  I don't mind the splitting pain.  I do mind the
"chase the nominal maintainer of obscure corner" pain.

If you really want it split: what about splitting off just the busy
and/or well-maintained subsystems?

  reply	other threads:[~2014-02-03  8:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31 15:53 [Qemu-devel] [PATCH 0/2] Use g_new() & friends where that makes obvious sense Markus Armbruster
2014-01-31 15:53 ` [Qemu-devel] [PATCH 1/2] qga: Fix memory allocation pasto Markus Armbruster
2014-01-31 16:06   ` Eric Blake
2014-01-31 15:53 ` [Qemu-devel] [PATCH 2/2] Use g_new() & friends where that makes obvious sense Markus Armbruster
2014-01-31 17:10   ` Eric Blake
2014-01-31 19:13     ` Richard Henderson
2014-02-03  8:56     ` Markus Armbruster
2014-01-31 16:13 ` [Qemu-devel] [PATCH 0/2] " Peter Maydell
2014-02-03  8:40   ` Markus Armbruster [this message]
2014-02-03  9:11     ` Peter Maydell
2014-02-04 16:52       ` Markus Armbruster
2014-02-04 17:27         ` Paolo Bonzini
2014-02-13 16:36       ` Markus Armbruster
2014-02-13 16:48         ` Peter Maydell
2014-02-13 19:30           ` Markus Armbruster
2014-02-18 15:32             ` Markus Armbruster
2014-02-21 11:10               ` Peter Maydell
2014-02-21 11:49                 ` Markus Armbruster
2014-02-21 11:52                   ` Peter Maydell
2014-02-21 12:37                     ` 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=87eh3kfv30.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=agraf@suse.de \
    --cc=aliguori@amazon.com \
    --cc=mdroth@linux.vnet.ibm.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.