From: cheetah <xuwh06@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] a newbie question: code patches
Date: Fri, 5 Aug 2011 01:56:10 -0700 [thread overview]
Message-ID: <CAMExZ1fjzx_pfWA88D5PL23o4DP2dj3534ThKe0Q2UyyLB-srw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 556 bytes --]
Hi folks,
I need to do some changes to qemu-kvm. However, on the kvm website, it is
suggested to develop against qemu.git. I am wondering if I develop against
qemu.git, because my fix may depend on some new patch that is only in
qemu.git, it seems very hard to generate a patch for the qemu-kvm. But my
goal is to generate a patch to qemu-kvm while contribute the patch to qemu.
Could you give me some advice? Should I develop again qemu.git or
qemu-kvm.git? How to manage the patch generating process less painful?
Thank you very much.
Regards,
Peter
[-- Attachment #2: Type: text/html, Size: 682 bytes --]
next reply other threads:[~2011-08-05 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 8:56 cheetah [this message]
2011-08-05 9:00 ` [Qemu-devel] a newbie question: code patches Stefan Hajnoczi
2011-08-05 9:04 ` cheetah
2011-08-05 9:10 ` Paolo Bonzini
2011-08-05 9:19 ` cheetah
2011-08-05 9:33 ` Stefan Hajnoczi
2011-08-05 9:37 ` cheetah
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=CAMExZ1fjzx_pfWA88D5PL23o4DP2dj3534ThKe0Q2UyyLB-srw@mail.gmail.com \
--to=xuwh06@gmail.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).