From: Jan Kiszka <jan.kiszka@web.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"David S. Ahern" <daahern@cisco.com>
Subject: Re: [Qemu-devel] State of EHCI emulation for QEMU
Date: Wed, 08 Dec 2010 09:32:00 +0100 [thread overview]
Message-ID: <4CFF4280.30702@web.de> (raw)
In-Reply-To: <4CFF4142.2090603@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
Am 08.12.2010 09:26, Gerd Hoffmann wrote:
> Hi,
>
>> It appears that the import of the ehci code to spice has completely lost
>> the development history and code contributions - from the original
>> version by Mark Burkley through the work I've done on it. Would you mind
>> pulling in the patch history instead of just the final code?
>
> I've first tried to rebase the ehci branch to latest master exactly to
> keep the history. Was quite messy with lots of conflicts though, so I
> gave up. For review & upstream merge having the whole history isn't
> that helpful anyway.
I'm was regularly merging master into ehci, and that worked quite well.
For the development phase, it might be nice to keep the history if
possible. But I agree that we need a clean series once upstream
submission is in sight.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2010-12-08 8:33 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 [this message]
2010-12-08 15:49 ` David S. Ahern
2010-12-08 17:14 ` Gerd Hoffmann
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=4CFF4280.30702@web.de \
--to=jan.kiszka@web.de \
--cc=Jes.Sorensen@redhat.com \
--cc=daahern@cisco.com \
--cc=kraxel@redhat.com \
--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).