From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56226) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bwFOo-0001ba-KA for qemu-devel@nongnu.org; Mon, 17 Oct 2016 17:24:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bwFOk-00072z-8e for qemu-devel@nongnu.org; Mon, 17 Oct 2016 17:24:46 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:34012) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1bwFOk-000723-0O for qemu-devel@nongnu.org; Mon, 17 Oct 2016 17:24:42 -0400 Received: from pps.filterd (m0098399.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u9HLOFcU140600 for ; Mon, 17 Oct 2016 17:24:40 -0400 Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by mx0a-001b2d01.pphosted.com with ESMTP id 2651gw5xbj-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Mon, 17 Oct 2016 17:24:40 -0400 Received: from localhost by e32.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 17 Oct 2016 15:24:39 -0600 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable From: Michael Roth In-Reply-To: References: <1476335734-29831-1-git-send-email-david@gibson.dropbear.id.au> <20161013222835.GP18039@umbus.fritz.box> <20161014102759.566a1c5e@bahia> <20161017165126.7445.53992@loki> <20161017181348.29726.67454@loki> Date: Mon, 17 Oct 2016 16:24:31 -0500 Message-Id: <20161017212431.29726.22702@loki> Subject: Re: [Qemu-devel] [Qemu-stable] [Qemu-ppc] [PULL 0/4] ppc patches for qemu-2.7 stable branch List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Thomas Huth , Greg Kurz , David Gibson , "qemu-ppc@nongnu.org" , qemu-stable , QEMU Developers Quoting Peter Maydell (2016-10-17 13:45:21) > On 17 October 2016 at 19:13, Michael Roth wro= te: > > We could do both though: use some ad-hoc way to tag for a particular > > sub-maintainer tree/stable branch, as well as an explicit "not for > > master" in the cover letter ensure it doesn't go into master. It's a bit > > more redundant, but flexible in that people can use whatever tagging > > format they want for a particular tree. > = > Yes, that would be my preference. Gmail's filtering is not > very good, and it doesn't seem to be able to support > multiple or complex matches on the subject line, but > it can deal with "doesn't include foo in body". > People who actively want to look for stuff not to go > into master can filter it however they like. Sounds good to me. For my part I think "for-2.7.1" etc. would be prefereable. No need to resend this patchset though. I suppose MAINTAINERS would be the best place to document something like this? > = > thanks > -- PMM >=20