From: "Andreas Färber" <afaerber@suse.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] x86 AREG0 patches
Date: Wed, 16 May 2012 05:44:28 +0200 [thread overview]
Message-ID: <4FB3229C.1030707@suse.de> (raw)
In-Reply-To: <CAAu8pHtcHydZ+dqX6vHVWsgmphCFqSm+UO8OqgLEgFNg=2znzA@mail.gmail.com>
Am 15.05.2012 19:22, schrieb Blue Swirl:
> On Mon, May 14, 2012 at 10:02 PM, Andreas Färber <afaerber@suse.de> wrote:
>> Am 13.05.2012 23:04, schrieb Blue Swirl:
>>> A preview of x86 AREG0 patches can be found at the usual place:
>>> URL git://repo.or.cz/qemu/blueswirl.git
>>> http://repo.or.cz/r/qemu/blueswirl.git
>>
>> It looks like that push has completely replaced your pending ppc conversion?
>
> Yes, I popped the StGit series before working on this, sorry. I really
> should try to use git branches.
If this StGit uses only one master branch, you can at least archive
multiple branches using
git push repo master:areg0-ppc
with repo as remote, master as local source branch and areg0-ppc as
remote destination branch name.
Locally you could create a branch with `git branch branchname`. `git
branch` tells you which branch you are on and `git checkout branchname`
switches between them. Pretty easy actually. The harder part is
organizing your branches in a way matching your workflows - I tend to do
lots of stuff in parallel, so by now I use at least ten local
repositories to avoid switching between branches and wasting time with
lengthy rebuilds, for working on different topics (e.g., master, 0.15,
ppc-next, s390-next, ARM, QOM).
I think Peter mentioned using StGit, and he maintains branches for his
PULLs.
>> If someone needs it for testing I still have a rebased version here:
>> http://repo.or.cz/w/qemu/afaerber.git/shortlog/refs/heads/ppc
>
> Would you like to start maintaining them in your queue?
I don't want qom-next to turn into a general-purpose master replacement.
Instead I would like Alex as ppc maintainer to decide on a sequence for
applying our series to ppc-next, and I'd either pull or cherry-pick the
QOM-related parts from there (don't think we have a conflict so far).
Note that my branch doesn't properly fix the build issue, it just added
a quick build fix on top for testing. On Alex' branch it seemed fixed
properly but wasn't rebased yet when I tested tcg/ppc64.
Andreas
--
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:[~2012-05-16 3:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 21:04 [Qemu-devel] x86 AREG0 patches Blue Swirl
2012-05-14 10:10 ` 陳韋任
2012-05-14 18:46 ` Blue Swirl
2012-05-14 22:02 ` Andreas Färber
2012-05-15 17:22 ` Blue Swirl
2012-05-16 3:44 ` 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=4FB3229C.1030707@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=blauwirbel@gmail.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 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).