xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: xen-devel@lists.xenproject.org, committers@xenproject.org,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: Commit moratorium for branching 4.7
Date: Tue, 7 Jun 2016 16:55:23 +0100	[thread overview]
Message-ID: <22358.61035.972745.598230@mariner.uk.xensource.com> (raw)
In-Reply-To: <5756DD13.2010001@citrix.com>

George Dunlap writes ("Re: Commit moratorium for branching 4.7"):
> On 07/06/16 15:26, Jan Beulich wrote:
> > Perhaps we can use the same model as I think we used last time,
> > with the person committing to unstable being responsible to also
> > put things applicable to 4.7 there? And with that declare the tree
> > open again for any changes not deemed likely to complicate
> > eventual backports to 4.7?
> +1



Xen-devel mailing list

  reply	other threads:[~2016-06-07 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <22358.51377.974810.863351@mariner.uk.xensource.com>
2016-06-07 13:55 ` Commit moratorium for branching 4.7 Ian Jackson
2016-06-07 14:26   ` Jan Beulich
2016-06-07 14:41     ` George Dunlap
2016-06-07 15:55       ` Ian Jackson [this message]
2016-06-07 16:00   ` Wei Liu

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22358.61035.972745.598230@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=committers@xenproject.org \
    --cc=george.dunlap@citrix.com \
    --cc=xen-devel@lists.xenproject.org \


* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).