|
From: | Gerd Hoffmann |
Subject: | Re: [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained? |
Date: | Fri, 11 Sep 2009 09:06:14 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3 |
Hi,
Closer to 20% I'd say. This is largely due to multiple versions of the same series. If there's a way to improve this, that would make my life a lot easier.
I think you should do smaller batches more frequently, i.e. commit 20 patches every day instead of >100 patches each week.
Advantages: * Patches don't hang around in staging forever, which makes everybody happy. * Patch ack-ing via qemu-commits works reasonable. * Reduce your workload: You can ask patch submitters to deal with merge conflicts then without making the merge process unreasonable slow. Just drop anything which doesn't apply as-is, ask the submitter to rebase+resend, pick up the fresh patches the next day. * I'd suspect we'll also have less patch conflicts in the first place then. Disadvantages: * Might be more testing work (how automated is this btw?).
Subject: [Qemu-devel] [PATCH 01/19] Suppress more more kraxelism Let's kick off this series with some of the more critical fixes. Signed-off-by: Mark McLoughlin<address@hidden>What would you be thinking hunting the commit log for some change and coming up with this?
I like that one, but it is a insider gag for qemu-commits readers and thus indeed not very useful when you'll read it a year or two in the future ...
cheers, Gerd
[Prev in Thread] | Current Thread | [Next in Thread] |