From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:35114) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLaab-0003nI-BI for qemu-devel@nongnu.org; Wed, 02 Nov 2011 09:10:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RLaaZ-000748-Sn for qemu-devel@nongnu.org; Wed, 02 Nov 2011 09:10:45 -0400 Received: from mail-yw0-f45.google.com ([209.85.213.45]:48644) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLaaZ-000744-QL for qemu-devel@nongnu.org; Wed, 02 Nov 2011 09:10:43 -0400 Received: by ywb3 with SMTP id 3so125873ywb.4 for ; Wed, 02 Nov 2011 06:10:43 -0700 (PDT) Message-ID: <4EB1414D.8070601@codemonkey.ws> Date: Wed, 02 Nov 2011 08:10:37 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <4EB09249.3050700@us.ibm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] We have now entered 1.0 hard freeze List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Max Filippov Cc: Blue Swirl , Stefan Weil , Anthony Liguori , qemu-devel 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. >