From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43166) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8PoH-0005tx-72 for qemu-devel@nongnu.org; Mon, 14 Dec 2015 04:52:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a8PoE-0001RP-02 for qemu-devel@nongnu.org; Mon, 14 Dec 2015 04:52:49 -0500 Received: from mx1.redhat.com ([209.132.183.28]:49038) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8PoD-0001RI-RM for qemu-devel@nongnu.org; Mon, 14 Dec 2015 04:52:45 -0500 References: <1450081359-7753-1-git-send-email-den@openvz.org> <20151214112012-mutt-send-email-mst@redhat.com> <566E8B39.5070202@openvz.org> <566E8BB0.4000303@redhat.com> <566E8EC5.7010103@openvz.org> <566E8F89.1040706@redhat.com> <566E90B5.3080203@openvz.org> From: Paolo Bonzini Message-ID: <566E9166.4060101@redhat.com> Date: Mon, 14 Dec 2015 10:52:38 +0100 MIME-Version: 1.0 In-Reply-To: <566E90B5.3080203@openvz.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH for 2.5? 1/1] DSDT: add floppy-related objects List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Denis V. Lunev" , "Michael S. Tsirkin" Cc: Eduardo Habkost , qemu-devel@nongnu.org, Yuri Pudgorodskiy , Roman Kagan , Igor Mammedov , Richard Henderson On 14/12/2015 10:49, Denis V. Lunev wrote: >> >> In any case, even if this is a bug that we want to add to 2.5.1, it's >> definitely too late for 2.5---at any time after soft freeze. > ok. 2.5.1 would be really great. Thank you for a prompt reply. > > Though I have a question about the freeze policy as > other people still accepting user-visible bugfixes > after a soft freeze. Of course things are up to the individual maintainer but, in general, I think that guest-visible changes should be vetted very carefully after soft freeze. It depends on the effect of the change. Changing ACPI tables is quite more far reaching than, say, fixing an infinite loop in a device model (which has never been triggered so far, or we would have had a bug reported). Paolo