qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>, Alexander Graf <agraf@suse.de>
Cc: Stefan Weil <sw@weilnetz.de>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 1.1-rc2 release
Date: Sat, 19 May 2012 19:02:43 +0000	[thread overview]
Message-ID: <CAAu8pHvpsCDuVh2=RhdvoW7rraTZu=Ro3dcApB7a4z7+cM8Hpw@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-B=FQvYSE=sDwe9tpQB5iZ-4Tu4xz3QMoo1A3VgKH8FQ@mail.gmail.com>

On Tue, May 15, 2012 at 8:33 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 15 May 2012 21:20, Anthony Liguori <anthony@codemonkey.ws> wrote:
>> On 05/15/2012 11:42 AM, Peter Maydell wrote:
>>> In this case it is a regression...
>
>> At what point did it regress?  I don't recall win64 ever working uner TCG...
>
> Sorry, I had in mind the mmap thing, and got confused with what
> I was quoting.
>
>>> Anyway, my point is not "these things must go in" but that it's very
>>> hard to tell from this side whether a patch is in the state:
>>>  (a) in your queue and will go into this rc
>>>  (b) missed the boat for this rc but will be in the next
>>>  (c) completely overlooked and needs pinging/yelling about
>>>  (d) judged not important enough to justify fixing in this release
>>
>> It's it not tagged '1.1' than I am not considering it for 1.1.
>>
>> If it's tagged with 1.1 *and* in a subsystem with an active submaintainer, I
>> would expect the submaintainer to handle it.  I do keep track of it though
>> until someone responds with "Thanks, Applied." and will follow up with
>> patches that fall into this category.
>
>> If you've posted a patch for 1.1 and it's a couple days old without
>> feedback, then you probably should ping the appropriate maintainer about it.
>>
>> FWIW, I don't see any pending 1.1 patches from you so I don't know if this
>> is a theoretical concern or a practical one.
>
> My current concern is
> http://patchwork.ozlabs.org/patch/158556/
> (submitted by Alex, although I see he forgot to tag it with "1.1").

Thanks, applied.

>
> I'll ping it...
>
> -- PMM
>

  parent reply	other threads:[~2012-05-19 19:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 16:04 [Qemu-devel] [ANNOUNCE] QEMU 1.1-rc2 release Anthony Liguori
2012-05-15 16:33 ` Stefan Weil
2012-05-15 16:38   ` Peter Maydell
2012-05-15 16:39     ` Anthony Liguori
2012-05-15 16:38   ` Anthony Liguori
2012-05-15 16:42     ` Peter Maydell
2012-05-15 20:20       ` Anthony Liguori
2012-05-15 20:33         ` Peter Maydell
2012-05-16  1:58           ` Andreas Färber
2012-05-19 19:02           ` Blue Swirl [this message]
2012-05-15 16:51     ` Stefan Weil
2012-05-15 16:37 ` Andreas Färber
2012-05-15 16:42   ` Anthony Liguori

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='CAAu8pHvpsCDuVh2=RhdvoW7rraTZu=Ro3dcApB7a4z7+cM8Hpw@mail.gmail.com' \
    --to=blauwirbel@gmail.com \
    --cc=agraf@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=anthony@codemonkey.ws \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).