public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
	quintela@redhat.com, qemu-devel@nongnu.org,
	kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call agenda for August 3
Date: Tue, 03 Aug 2010 16:49:41 +0300	[thread overview]
Message-ID: <4C581E75.30104@redhat.com> (raw)
In-Reply-To: <4C581A4D.6050209@codemonkey.ws>

  On 08/03/2010 04:31 PM, Anthony Liguori wrote:
> On 08/03/2010 08:16 AM, Avi Kivity wrote:
>>  On 08/03/2010 04:01 PM, Luiz Capitulino wrote:
>>> On Tue, 03 Aug 2010 01:46:01 +0200
>>> Juan Quintela<quintela@redhat.com>  wrote:
>>>
>>>> Please send in any agenda items you are interested in covering.
>>> - 0.13
>>
>> More specifically, 0.13-rc0.  Tagged but not announced?  I'd like to 
>> announce it so people can start testing it.
>
> That's the normal process.  0.13.0-rc0 is just a git snapshot and as 
> such, everyone has been testing it already.  0.13.0-rc1 is due to be 
> tagged later today and that's the first one that's useful to test 
> separately.

I meant users.  Many users avoid git and test tarballs which come from 
an announcement instead.  Same for distros, things like rawhide can 
package an -rc0.

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


  reply	other threads:[~2010-08-03 13:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02 23:46 KVM call agenda for August 3 Juan Quintela
2010-08-03  0:21 ` Miguel Di Ciurcio Filho
2010-08-03 13:01 ` [Qemu-devel] " Luiz Capitulino
2010-08-03 13:16   ` Avi Kivity
2010-08-03 13:31     ` Anthony Liguori
2010-08-03 13:49       ` Avi Kivity [this message]
2010-08-03 14:25         ` Anthony Liguori
2010-08-03 14:29           ` Avi Kivity

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=4C581E75.30104@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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