All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>, Greg Kurz <groug@kaod.org>,
	"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	qemu-stable <qemu-stable@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-stable] [Qemu-ppc] [PULL 0/4] ppc patches for qemu-2.7 stable branch
Date: Tue, 25 Oct 2016 18:57:33 -0500	[thread overview]
Message-ID: <20161025235733.17113.25771@loki> (raw)
In-Reply-To: <20161025014129.GN11052@umbus.fritz.box>

Quoting David Gibson (2016-10-24 20:41:29)
> On Mon, Oct 17, 2016 at 04:24:31PM -0500, Michael Roth wrote:
> > Quoting Peter Maydell (2016-10-17 13:45:21)
> > > On 17 October 2016 at 19:13, Michael Roth <mdroth@linux.vnet.ibm.com> wrote:
> > > > 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?
> 
> So.. regardless of the outcome in general for future stable merges..
> 
> Has this batch been merged for 2.7 stable?  Or do I need to resend it
> in the new style?

No need to resend. I should have the initial staging tree for 2.7 posted
by Monday and will have this included.

> 
> -- 
> David Gibson                    | I'll have my music baroque, and my code
> david AT gibson.dropbear.id.au  | minimalist, thank you.  NOT _the_ _other_
>                                 | _way_ _around_!
> http://www.ozlabs.org/~dgibson

  reply	other threads:[~2016-10-25 23:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13  5:15 [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch David Gibson
2016-10-13  5:15 ` [Qemu-devel] [PULL 1/4] linux-headers: update David Gibson
2016-10-13  5:15 ` [Qemu-devel] [PULL 2/4] hw/ppc/spapr: Move code related to "ibm, pa-features" to a separate function David Gibson
2016-10-13  5:15 ` [Qemu-devel] [PULL 3/4] hw/ppc/spapr: Fix the selection of the processor features David Gibson
2016-10-13  5:15 ` [Qemu-devel] [PULL 4/4] ppc: Check the availability of transactional memory David Gibson
2016-10-13 11:54 ` [Qemu-devel] [PULL 0/4] ppc patches for qemu-2.7 stable branch Peter Maydell
2016-10-13 11:57   ` Peter Maydell
2016-10-13 22:28     ` David Gibson
2016-10-14  8:27       ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2016-10-14 17:38         ` Peter Maydell
2016-10-17  7:44           ` Thomas Huth
2016-10-17 16:51             ` [Qemu-devel] [Qemu-stable] " Michael Roth
2016-10-17 17:33               ` Peter Maydell
2016-10-17 18:13                 ` Michael Roth
2016-10-17 18:45                   ` Peter Maydell
2016-10-17 21:24                     ` Michael Roth
2016-10-17 21:49                       ` Peter Maydell
2016-10-25  1:41                       ` David Gibson
2016-10-25 23:57                         ` Michael Roth [this message]
2016-11-01  2:26                           ` David Gibson
2016-11-02 23:49                             ` Michael Roth

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=20161025235733.17113.25771@loki \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=groug@kaod.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=thuth@redhat.com \
    /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.