All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, Ian.Jackson@eu.citrix.com
Cc: jbeulich@suse.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] MAINTAINERS: stable backports should be requested on xen-devel
Date: Tue, 8 Sep 2015 14:42:55 +0100	[thread overview]
Message-ID: <1441719775.24450.104.camel@citrix.com> (raw)
In-Reply-To: <20150908132040.GE12714@zion.uk.xensource.com>

On Tue, 2015-09-08 at 14:20 +0100, Wei Liu wrote:
> On Tue, Sep 08, 2015 at 12:37:04PM +0100, Ian Campbell wrote:
> > On Sat, 2015-07-25 at 09:25 +0100, Ian Campbell wrote:
> > > As well as CC-ing the correct people. I just saw such a request on
> > > xen-users and thought this was worth clarifying here too.
> > > 
> > > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> > 
> > Just found this in my folder, do we want to take it for 4.6?
> > 
> 
> Fine by me of course.

AIUI the branching process involves tweaking this text to refer to the
specific maintainers of the given stable branch.

IOW I think the "backport" of this might be a little more involved, but
hopefully fairly obvious -- Ian, do you think you can deal with it?

$ git diff origin/staging-4.5 origin/staging -- MAINTAINERS | filterdiff -#1
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -49,14 +49,9 @@ for inclusion in xen-unstable.
 Please see http://wiki.xen.org/wiki/Xen_Maintenance_Releases for more
 information.
 
-Remember to copy the stable branch maintainer. The maintainer for this
-branch is:
-
-	Jan Beulich <jbeulich@suse.com>
-
-Tools backport requests should also be copied to:
-
-	Ian Jackson <Ian.Jackson@eu.citrix.com>
+Remember to copy the appropriate stable branch maintainer who will be
+listed in this section of the MAINTAINERS file in the appropriate
+branch.
 
 	Unstable Subsystem Maintainers
 	==============================
> 
> > > ---
> > >  MAINTAINERS | 7 ++++---
> > >  1 file changed, 4 insertions(+), 3 deletions(-)
> > > 
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index a4e64ea..156a95f 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -49,9 +49,10 @@ for inclusion in xen-unstable.
> > >  Please see http://wiki.xen.org/wiki/Xen_Maintenance_Releases for
> > > more
> > >  information.
> > >  
> > > -Remember to copy the appropriate stable branch maintainer who will
> > > be
> > > -listed in this section of the MAINTAINERS file in the appropriate
> > > -branch.
> > > +Backport requests should be made on the 
> > > xen-devel@lists.xenproject.org
> > > +list. Remember to copy the appropriate stable branch maintainer who
> > > +will be listed in this section of the MAINTAINERS file in the
> > > +appropriate branch.
> > >  
> > >  	Unstable Subsystem Maintainers
> > >  	==============================

  reply	other threads:[~2015-09-08 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-25  8:25 [PATCH] MAINTAINERS: stable backports should be requested on xen-devel Ian Campbell
2015-09-08 11:37 ` Ian Campbell
2015-09-08 13:19   ` Jan Beulich
2015-09-08 13:20   ` Wei Liu
2015-09-08 13:42     ` Ian Campbell [this message]
2015-09-08 14:38       ` Ian Jackson
2015-09-08 14:51         ` Ian Campbell

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=1441719775.24450.104.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.