qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Planning for the 0.11.0 release
Date: Sun, 12 Jul 2009 11:31:24 +0300	[thread overview]
Message-ID: <4A599F5C.8040009@redhat.com> (raw)
In-Reply-To: <4A57751E.3070005@us.ibm.com>

On 07/10/2009 08:06 PM, Anthony Liguori wrote:
> BTW, this is one of the challenges of doing pulls.  I did the pull and 
> then deleted every qemu-io patch in my queue since I assumed that 
> everything that should go in was part of hch's pull request.  In 
> general, that's the only sane way to do pulls so if someone requests a 
> pull in the future, please make sure that you've gone through and 
> pulled any patch from the list first.

Pulls and stale queues are incompatible.  So long as everything is in 
patches, it doesn't matter since duplicate patches won't apply.  However 
a branch can't be based on a queue (since that's liable to change any 
time), and the branch can't commit and patches in the queue (since the 
queue might be committed any time).  If you want to pull, you'll need to 
shorten your queues (that will improve many other people's quality of 
life, btw).


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

      reply	other threads:[~2009-07-12  8:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 23:57 [Qemu-devel] Planning for the 0.11.0 release Anthony Liguori
2009-06-23 12:12 ` Avi Kivity
2009-06-23 15:09 ` Blue Swirl
2009-06-23 15:47   ` Anthony Liguori
2009-06-23 15:49   ` Avi Kivity
2009-07-09  8:27 ` Mark McLoughlin
2009-07-09 13:32   ` Anthony Liguori
2009-07-10  1:10     ` Markus Armbruster
2009-07-10 13:53       ` Anthony Liguori
2009-07-10 15:04         ` Jan Kiszka
2009-07-10 15:49           ` Anthony Liguori
2009-07-10 16:23             ` Jan Kiszka
2009-07-10 16:33               ` Anthony Liguori
2009-07-10 16:52                 ` Jan Kiszka
2009-07-10 17:03                   ` Anthony Liguori
2009-07-10 17:15                     ` Jan Kiszka
2009-07-10 17:40                     ` Paul Brook
2009-07-10 17:58                       ` Anthony Liguori
2009-07-10 18:02                       ` Jan Kiszka
2009-07-10 18:22                         ` Paul Brook
2009-07-10 16:55             ` Kevin Wolf
2009-07-10 16:59               ` Anthony Liguori
2009-07-10 17:10                 ` Kevin Wolf
2009-07-10 17:31                   ` Anthony Liguori
2009-07-10 17:10                 ` Christoph Hellwig
2009-07-10 17:12                   ` Kevin Wolf
2009-07-10 18:26                     ` Christoph Hellwig
2009-07-10 17:29                   ` Anthony Liguori
2009-07-10 18:13                     ` Christoph Hellwig
2009-07-10 18:29                       ` Anthony Liguori
2009-07-10 17:06               ` Anthony Liguori
2009-07-12  8:31                 ` 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=4A599F5C.8040009@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.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).