From: Gerd Hoffmann <kraxel@redhat.com>
To: "David Ahern (daahern)" <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: Thu, 09 Dec 2010 14:05:33 +0100 [thread overview]
Message-ID: <4D00D41D.3000204@redhat.com> (raw)
In-Reply-To: <45F31A3DE872BB4A981B8851F234387103B3B72E@xmb-sjc-217.amer.cisco.com>
Hi,
> New features developed for the kernel are done in a separate git trees.
> When a feature is ready for inclusion into the main kernel tree, a pull
> request is sent. That workflow maintains a complete change history for
> the feature. Take performance events for example: you can go into Linus'
> git tree and see the complete history of changes. There's no reason the
> same methodology cannot be done for qemu.
It is done for qemu, pci and block are maintained that way for example.
The key difference is that the patches which are accepted into the
subsystem branches and then are pulled go through a full review @
qemu-devel before.
cheers,
Gerd
next prev parent reply other threads:[~2010-12-09 13:06 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
2010-12-08 17:41 ` David Ahern (daahern)
2010-12-09 13:05 ` Gerd Hoffmann [this message]
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=4D00D41D.3000204@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.