From: "Andreas Färber" <afaerber@suse.de>
To: Laszlo Ersek <lersek@redhat.com>
Cc: peter.maydell@linaro.org, stefano.stabellini@eu.citrix.com,
qemu-devel@nongnu.org, mtosatti@redhat.com, agraf@suse.de,
Markus Armbruster <armbru@redhat.com>,
borntraeger@de.ibm.com, mkletzan@redhat.com, pbonzini@redhat.com,
rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v2 0/8] Guest memory allocation fixes & cleanup
Date: Wed, 31 Jul 2013 16:00:16 +0200 [thread overview]
Message-ID: <51F91870.7020306@suse.de> (raw)
In-Reply-To: <51F9040F.1040104@redhat.com>
Am 31.07.2013 14:33, schrieb Laszlo Ersek:
> On 07/31/13 10:50, Markus Armbruster wrote:
>> Markus Armbruster <armbru@redhat.com> writes:
>>
>>> Ping?
>>
>> Has been ignored for six weeks, and now it no longer applies. Rebased
>> version coming.
>>
>> *Sigh*
>
> Why haven't you been made a maintainer yet? You could have a
> "cleanup-fubars" tree and you could send pull requests for cleanups.
>
> What you're doing is (apparently) unpopular to review, but critically
> important for long-term health. Everyone is overloaded and concentrating
> on important features and bugfixes with high visibility. Refactoring
> falls of the wagon.
Paolo and me will disagree, but sadly whenever you do one refactoring,
you can't help but notice that there's more things that could use some
refactoring, too. Where we get back to priorities and time and the need
for spreading the load over more shoulders. ;)
Andreas
> Which is exactly why you should be able to send pull
> requests.
>
> Laszlo
>
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2013-07-31 20:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 7:54 [Qemu-devel] [PATCH v2 0/8] Guest memory allocation fixes & cleanup Markus Armbruster
2013-06-20 7:54 ` [Qemu-devel] [PATCH v2 1/8] exec: Fix Xen RAM allocation with unusual options Markus Armbruster
2013-06-20 7:54 ` [Qemu-devel] [PATCH v2 2/8] exec: Clean up fall back when -mem-path allocation fails Markus Armbruster
2013-06-20 7:54 ` [Qemu-devel] [PATCH v2 3/8] exec: Reduce ifdeffery around -mem-path Markus Armbruster
2013-06-20 7:54 ` [Qemu-devel] [PATCH v2 4/8] exec: Simplify the guest physical memory allocation hook Markus Armbruster
2013-06-20 7:54 ` [Qemu-devel] [PATCH v2 5/8] exec: Drop incorrect & dead S390 code in qemu_ram_remap() Markus Armbruster
2013-06-20 7:54 ` [Qemu-devel] [PATCH v2 6/8] exec: Clean up unnecessary S390 ifdeffery Markus Armbruster
2013-06-20 7:54 ` [Qemu-devel] [PATCH v2 7/8] exec: Don't abort when we can't allocate guest memory Markus Armbruster
2013-06-20 7:54 ` [Qemu-devel] [PATCH v2 8/8] pc_sysfw: Fix ISA BIOS init for ridiculously big flash Markus Armbruster
2013-06-24 14:22 ` [Qemu-devel] [PATCH v2 0/8] Guest memory allocation fixes & cleanup Martin Kletzander
2013-07-18 16:31 ` Markus Armbruster
2013-07-31 8:50 ` Markus Armbruster
2013-07-31 12:33 ` Laszlo Ersek
2013-07-31 14:00 ` Andreas Färber [this message]
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=51F91870.7020306@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=lersek@redhat.com \
--cc=mkletzan@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefano.stabellini@eu.citrix.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).