From: Chunyan Liu <cyliu@suse.com>
To: xen-devel@lists.xen.org
Cc: wei.liu2@citrix.com, jfehlig@suse.com, Ian.Jackson@eu.citrix.com,
ian.campbell@citrix.com, Chunyan Liu <cyliu@suse.com>
Subject: [RFC Doc V11 0/4] domain snapshot document
Date: Tue, 11 Aug 2015 18:44:12 +0800 [thread overview]
Message-ID: <1439289856-27802-1-git-send-email-cyliu@suse.com> (raw)
Changes to V10:
- several updates to xl design and libxl design to address comments on V10.
- few updates to keep consitent with code implementation
V10:
http://lists.xenproject.org/archives/html/xen-devel/2015-01/msg03071.html
Codes implementation is posted right after.
next reply other threads:[~2015-08-11 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 10:44 Chunyan Liu [this message]
2015-08-11 10:44 ` [RFC Doc V11 1/5] domain snapshot terms Chunyan Liu
2015-08-11 10:44 ` [RFC Doc V11 2/5] domain snapshot introduction Chunyan Liu
2015-08-11 10:44 ` [RFC Doc V11 3/5] domain snapshot xl design Chunyan Liu
2015-08-11 10:44 ` [RFC Doc V11 4/5] domain snapshot libxl design Chunyan 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:
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=1439289856-27802-1-git-send-email-cyliu@suse.com \
--to=cyliu@suse.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=jfehlig@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 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).