All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Stefan Weil <weil@mail.berlios.de>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] We have now entered 1.0 hard freeze
Date: Wed, 02 Nov 2011 08:10:37 -0500	[thread overview]
Message-ID: <4EB1414D.8070601@codemonkey.ws> (raw)
In-Reply-To: <CAMo8Bf+7RoWtXZX-BiHxrS+c7bE5BK5iz_dFzRP+0GEJ6tO4LA@mail.gmail.com>

On 11/02/2011 08:08 AM, Max Filippov wrote:
> Hi.
>
>> If you're a contributor and have a question about a patch that didn't make
>> the hard freeze, please feel free to ask about it, but at this point, it's
>> very unlikely to make it to 1.0.
>
> My pull request for the xtensa
> (http://lists.nongnu.org/archive/html/qemu-devel/2011-10/msg03962.html)
> haven't got any attention.

I'm expecting Blue to pull that.  It made it in time for 1.0.  The same is true 
for TCGi.

> I can resend it, should you reconsider applying it, or I can resend
> only 'fixes'-part of it.
>
> And also I'd like it to be clarified, whether I should consider myself
> a contributor or a submaintainer.

If you do PULL requests, you're a submaintainer :-)

Regards,

Anthony Liguori

>> If you're a submaintainer, it's up to you about whether you continue taking
>> new features into your tree during the freeze.  I would strongly encourage
>> it.  But only send pull requests that contain bug fixes from this point on.
>

  reply	other threads:[~2011-11-02 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02  0:43 [Qemu-devel] We have now entered 1.0 hard freeze Anthony Liguori
2011-11-02  8:10 ` Alon Levy
2011-11-02 13:08 ` Max Filippov
2011-11-02 13:10   ` Anthony Liguori [this message]
2011-11-02 13:21     ` Peter Maydell
2011-11-02 20:00     ` Blue Swirl
2011-11-02 22:14 ` Rick Vernam

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=4EB1414D.8070601@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.