On 16.04.2012, at 21:46, Blue Swirl wrote: > On Mon, Apr 16, 2012 at 19:28, Peter Maydell <peter.mayd...@linaro.org> wrote: >> On 16 April 2012 20:12, Blue Swirl <blauwir...@gmail.com> wrote: >>> On Mon, Apr 16, 2012 at 16:53, Alexander Graf <ag...@suse.de> wrote: >>>> If you can update it on top of ppc-next and add patch descriptions >>>> in every patch (more than just the subject line), I'll happily apply >>>> it and if possible also pull it in before the hard freeze. >>> >>> OK. Thanks for the review. But I'd prefer to apply them directly to >>> qemu.git, because I'm using StGit for the patch stack and it doesn't >>> work with different branches. >> >> I use stgit a lot and I haven't run into this issue yet... Couple >> of approaches that spring to mind: >> 1. use "stg rebase ppc-next" to put your patch stack on top of >> ppc-next (This is how I did the recent cp15-rework series which sits >> on top of the drop-cpu_reset_model_id patchset, for instance.) >> 2. create a new branch starting from ppc-next and stg pick the relevant >> patches into it. (I use that for sending subsets of omap related patches >> from qemu-linaro.) > > Thanks, cool. I'll try that. I'm considering dropping stgit (it has > emptied too many patches) and use plain git, this way I could start > using branches.
So how are things going there? Apparently all the patches from ppc-next should be in mainline, Andreas is happy with the state of QOM on PPC as it is by now too, so it's a perfect point in time to do this change! Alex