public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Umesh Deshpande <udeshpan@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [RFC 1/4] A separate thread for the VM migration
Date: Wed, 20 Jul 2011 11:14:34 +0300	[thread overview]
Message-ID: <4E268E6A.7080208@redhat.com> (raw)
In-Reply-To: <1202301493.1447250.1311134185524.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com>

On 07/20/2011 06:56 AM, Umesh Deshpande wrote:

<snip>

Please give each patch a separate, meaningful title and post them in 
their own thread.

See

    git format-patches --cover-letter
    git send-email

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2011-07-20  8:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <415961500.1446235.1311128175880.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com>
2011-07-20  3:56 ` [RFC 1/4] A separate thread for the VM migration Umesh Deshpande
2011-07-20  8:14   ` Avi Kivity [this message]

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=4E268E6A.7080208@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=udeshpan@redhat.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