From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56098) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFilf-00023n-N6 for qemu-devel@nongnu.org; Tue, 18 Feb 2014 06:23:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WFilZ-0006YJ-O5 for qemu-devel@nongnu.org; Tue, 18 Feb 2014 06:23:15 -0500 Received: from mail-la0-f45.google.com ([209.85.215.45]:37246) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFilZ-0006Y3-GP for qemu-devel@nongnu.org; Tue, 18 Feb 2014 06:23:09 -0500 Received: by mail-la0-f45.google.com with SMTP id b8so12244397lan.32 for ; Tue, 18 Feb 2014 03:23:08 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <5303411A.5080601@redhat.com> References: <1392647854-8067-1-git-send-email-peter.maydell@linaro.org> <53025C08.2030207@redhat.com> <5302B11F.1070400@suse.de> <53033261.7020100@suse.de> <5303411A.5080601@redhat.com> From: Peter Maydell Date: Tue, 18 Feb 2014 11:22:48 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH 0/3] ARM: three easy patches for coverity-reported issues List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-stable , Patch Tracking , =?UTF-8?Q?Andreas_F=C3=A4rber?= , QEMU Developers On 18 February 2014 11:16, Paolo Bonzini wrote: > Il 18/02/2014 12:09, Peter Maydell ha scritto: > >> > No, we've had that topic before: It's your job as submitter and >> > maintainer to flag that appropriately in the commit message, as per QEMU >> > Summit 2012. >> >> I don't think this workflow works. I have no idea what >> stable's criteria are, and if you rely on people >> adding a cc you're going to miss stuff. > > > There isn't really a standard criterion. It's up to each maintainer to be > stricter or looser on what goes to stable. My criteria for ARM in the past has typically been "there's a new release every three months, anything that got past the release testing process for release N is sufficiently non-critical it can just go into release N+1". thanks -- PMM