qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zhi Yong Wu <zwu.kernel@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Jan Kiszka <jan.kiszka@web.de>,
	Wayne Xia <xiawenc@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/3] kvm:showing a splash picture when start
Date: Thu, 23 Jun 2011 19:56:43 +0800	[thread overview]
Message-ID: <BANLkTimHg1uYAkd_aVurHq7OvjGBWb=KJg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin_95kskBprYirVSjfctOnKw5kUGQ@mail.gmail.com>

I guess that Wayne should target qemu-kvm git tree.

Regards,

Zhiyong Wu

On Thu, Jun 23, 2011 at 7:14 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> 2011/6/23 Jan Kiszka <jan.kiszka@web.de>:
>> On 2011-06-23 11:18, Wayne Xia wrote:
>>> Hi,
>>>     these 3 patch simply enable qemu-kvm to show a logo picture when it
>>
>> You are posting on qemu-devel (which is correct for this topic), so your
>> patches must target that tree. Patch 1 eg. does not and needs rebasing.
>
> More specifically, develop code against qemu.git as a default.   Much
> of the development that goes into qemu-kvm actually comes via
> qemu.git.  If you need to do qemu-kvm.git specific stuff, you'll know.
>
> Additional info:
> "The QEMU codebase is known as qemu.git. That's the git repository
> that holds the QEMU source code history. The KVM codebase is known as
> qemu-kvm.git, the git repository that holds the KVM source code
> history.
>
> The relationship between qemu.git and qemu-kvm.git is as follows.
> qemu-kvm.git is a fork of qemu.git and periodically merges updates
> from qemu.git back into qemu-kvm.git. A lot of code changes are merged
> into qemu.git and become available in qemu-kvm.git after the next
> periodic merge. KVM-specific enhancements may be merged into
> qemu-kvm.git and may be sent back upstream to qemu.git.
>
> Efforts are underway to completely merge qemu-kvm.git into qemu.git.
> This will make qemu-kvm.git obsolete and result in a single codebase.
> In the future there may only be a qemu package."
>
> http://blog.vmsplice.net/2011/03/should-i-use-qemu-or-kvm.html
>
> Stefan
>
>



-- 
Regards,

Zhi Yong Wu

  parent reply	other threads:[~2011-06-23 11:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23  9:18 [Qemu-devel] [PATCH v2 0/3] kvm:showing a splash picture when start Wayne Xia
2011-06-23 10:03 ` Jan Kiszka
2011-06-23 11:14   ` Stefan Hajnoczi
2011-06-23 11:17     ` Jan Kiszka
2011-06-23 12:33       ` Stefan Hajnoczi
2011-06-23 12:36         ` Avi Kivity
2011-06-23 11:56     ` Zhi Yong Wu [this message]
2011-06-23 11:57       ` Jan Kiszka
2011-06-23 12:05         ` Zhi Yong Wu
2011-06-23 11:20   ` Wayne Xia
2011-06-23 11:24     ` Jan Kiszka
2011-06-23 12:05       ` Daniel P. Berrange
2011-06-23 12:29         ` Jan Kiszka
2011-06-23 14:46           ` Andreas Färber
2011-06-24  2:28           ` Wayne Xia
2011-06-23 11:46     ` Daniel P. Berrange
2011-06-23 11:41 ` Daniel P. Berrange
2011-06-23 12:00 ` Richard W.M. Jones
2011-06-23 13:38   ` Michael Tokarev
2011-06-23 14:59   ` Anthony Liguori

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='BANLkTimHg1uYAkd_aVurHq7OvjGBWb=KJg@mail.gmail.com' \
    --to=zwu.kernel@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@web.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=xiawenc@linux.vnet.ibm.com \
    /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).