All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org,
	tamas.lengyel@zentific.comoleksandr.tyshchenko,
	Razvan Cojocaru <rcojocaru@bitdefender.com>
Subject: Re: Xen 4.6 Development Update (three months reminder)
Date: Wed, 15 Apr 2015 10:09:10 +0100	[thread overview]
Message-ID: <1429088950.15516.144.camel@citrix.com> (raw)
In-Reply-To: <20150414103748.GS17670@zion.uk.xensource.com>

On Tue, 2015-04-14 at 11:37 +0100, Wei Liu wrote:
> On Tue, Apr 14, 2015 at 01:34:45PM +0300, Razvan Cojocaru wrote:
> > On 04/14/2015 01:27 PM, wei.liu2@citrix.com wrote:
> > > *  VM event patches (none)
> > >    Add support for XSETBV vm_events,
> > >    Support hybernating guests
> > >    Support for VMCALL-based vm_events
> > >   -  Razvan Cojocaru
> > 
> > These depend on Tamas' Clean-up of mem-event subsystem series (which
> > hasn't been applied in its entirety). If you prefer, I can apply Tamas'
> > patches manually on a fresh Xen mainline copy and start sending out our
> > patches built on top of that.
> > 
> > What do you think?
> > 
> 
> This email is just a general reminder of our development cycle.
> 
> There is no need to rush IMHO. You still have several months.

More generally though it is find IMHO to send out a series which depends
on another so long as the 00/NN email clearly explains what it needs to
be applied on top of (i.e. a reference to the specific version of the
other series).

You should omit that other tree when posting, by passing git send-email
the correct range to just send your own stuff.

And under such circumstances it might also be a good idea to also
include a git url, to make it easier for people to pickup the right set
of things.

Ian.

  reply	other threads:[~2015-04-15  9:09 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 10:27 Xen 4.6 Development Update (three months reminder) wei.liu2
2015-04-14 10:34 ` Razvan Cojocaru
2015-04-14 10:37   ` Wei Liu
2015-04-15  9:09     ` Ian Campbell [this message]
2015-04-14 12:25 ` Jaggi, Manish
2015-04-14 12:34   ` Julien Grall
2015-04-14 14:26     ` Ian Campbell
2015-04-14 14:57       ` Jaggi, Manish
2015-04-14 13:28 ` Andrew Cooper
2015-04-14 13:33   ` Wei Liu
2015-04-14 18:51     ` Elena Ufimtseva
2015-04-14 13:33 ` George Dunlap
2015-04-14 14:01   ` Meng Xu
2015-04-15  2:34   ` Chun Yan Liu
2015-04-14 13:35 ` Tamas Lengyel
2015-04-14 13:48   ` Jan Beulich
2015-04-14 13:52     ` Wei Liu
2015-04-15  9:11       ` Ian Campbell
2015-04-15  9:18         ` Jan Beulich
2015-04-15 16:01           ` Lars Kurth
2015-04-14 14:16 ` Boris Ostrovsky
2015-04-14 15:37 ` Konrad Rzeszutek Wilk
2015-04-28 17:17 ` Jim Fehlig
2015-04-28 22:17   ` Jim Fehlig
2015-04-29  0:21     ` Andrew Cooper
2015-04-29 10:23       ` Fabio Fantoni
2015-04-29 12:44         ` Fabio Fantoni
2015-05-04  9:50           ` Wei Liu
2015-04-29 16:39         ` Jim Fehlig
2015-04-30 10:31           ` Fabio Fantoni
2015-04-30 16:55             ` Jim Fehlig
2015-05-01  8:36               ` Fabio Fantoni
2015-05-01 20:45                 ` Jim Fehlig
2015-05-04  6:05 ` Yu, Zhang
2015-05-04  9:44   ` Wei Liu
2015-05-04 12:51     ` Yu, Zhang
2015-05-05  9:12       ` Wei Liu
2015-05-05 13:12         ` Yu, Zhang

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=1429088950.15516.144.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=rcojocaru@bitdefender.com \
    --cc=tamas.lengyel@zentific.comoleksandr.tyshchenko \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.