From: Gerd Hoffmann <kraxel@redhat.com>
To: "David S. Ahern" <daahern@cisco.com>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>,
Jan Kiszka <jan.kiszka@web.de>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] State of EHCI emulation for QEMU
Date: Wed, 08 Dec 2010 18:14:10 +0100 [thread overview]
Message-ID: <4CFFBCE2.1010909@redhat.com> (raw)
In-Reply-To: <4CFFA904.7030508@cisco.com>
Hi,
> Where was the messiness given that most of the changes are to a brand
> new file?
From the "devel -> merge with upstream -> fixup breakage + commit ->
devel" cycle. When rebasing *that* you simply don't get a nice +
bisectable patch series. Early patches didn't apply cleanly due to
buildsystem changes. After fixing up that ehci didn't build. Of course
there are likely fixup patches coming later which solve that which I
could try to find + cherry-pick + squash-in. But at that point I felt
it simply isn't worth the trouble given that we would squash it all
together anyway for patch review + upstream merge.
cheers,
Gerd
next prev parent reply other threads:[~2010-12-08 17:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-13 19:28 [Qemu-devel] State of EHCI emulation for QEMU Jan Kiszka
2010-12-04 0:18 ` Gerd Hoffmann
2010-12-04 9:05 ` Jan Kiszka
2010-12-04 20:21 ` David S. Ahern
2010-12-08 8:26 ` Gerd Hoffmann
2010-12-08 8:32 ` Jan Kiszka
2010-12-08 15:49 ` David S. Ahern
2010-12-08 17:14 ` Gerd Hoffmann [this message]
2010-12-08 17:41 ` David Ahern (daahern)
2010-12-09 13:05 ` Gerd Hoffmann
2010-12-09 20:32 ` David S. Ahern
2010-12-11 10:42 ` Blue Swirl
2010-12-08 8:18 ` Gerd Hoffmann
2010-12-08 8:24 ` Jan Kiszka
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=4CFFBCE2.1010909@redhat.com \
--to=kraxel@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=daahern@cisco.com \
--cc=jan.kiszka@web.de \
--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.