qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: cheetah <xuwh06@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] a newbie question: code patches
Date: Fri, 5 Aug 2011 10:33:59 +0100	[thread overview]
Message-ID: <CAJSP0QVVYYd4kUUCe7bQOpOsdAFOb_E-6M0njch2paV_bnUf4Q@mail.gmail.com> (raw)
In-Reply-To: <CAMExZ1fAx8wR2z6sjWKe15pQOeHZGiYRROdofnt48pRuu0C7Hg@mail.gmail.com>

On Fri, Aug 5, 2011 at 10:19 AM, cheetah <xuwh06@gmail.com> wrote:
> Sounds great. Thanks.
> I am a newbie and still confusing on how to do it. Please excuse my
> ignorance.
> If I forked a my own branch on qemu.git and develop against it.
> For instance I change qcow2.c which depends on some functions in block.c
> which are different from qemu-kvm.git because qemu-kvm.git has an old
> version of block.c
> In this case I need to generate a patch for both qcow2.c and block.c by diff
> with the qemu-kvm.git's version. This is done manually. And if more files
> are involved, it becomes really painful.
> Is there any better way to generate a patch for qemu-kvm.git easily?

The block layer is the same in qemu-kvm.git.  The will be zero or very
few conflicts, so developing against qemu.git is the right thing.  For
performance testing you may wish to git format-patch and apply those
patches to a qemu-kvm.git tree.

Please share what you plan to work on with the community.  This can
save you a lot of time and avoid duplicating work.  Before you post,
check out the "block layer roadmap thread" which lists many of the
proposed changes that have been discussed:
http://lists.gnu.org/archive/html/qemu-devel/2011-07/msg03162.html

If you send an email explaining what you'd like to change you'll get
advice on how to get started.

Stefan

  reply	other threads:[~2011-08-05  9:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05  8:56 [Qemu-devel] a newbie question: code patches cheetah
2011-08-05  9:00 ` 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 [this message]
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=CAJSP0QVVYYd4kUUCe7bQOpOsdAFOb_E-6M0njch2paV_bnUf4Q@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xuwh06@gmail.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).