From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jan Beulich <jbeulich@suse.com>
Subject: [PATCH 2/4] Update version to Xen 4.6 RC
Date: Tue, 11 Aug 2015 15:09:18 +0100 [thread overview]
Message-ID: <1439302160-24633-3-git-send-email-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <1439302160-24633-1-git-send-email-ian.jackson@eu.citrix.com>
* Change README to say `Xen 4.6-rc'
* Change XEN_EXTRAVERSION so that we are `4.6.0-rc'
Note that the RC number (eg, 1 for rc1) is not in the version string,
so that we do not need to update this again when we cut the next RC.
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
CC: Jan Beulich <jbeulich@suse.com>
CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
CC: Ian Campbell <ian.campbell@citrix.com>
CC: Wei Liu <wei.liu2@citrix.com>
---
README | 12 ++++++------
xen/Makefile | 2 +-
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/README b/README
index 0e456b8..522f1a2 100644
--- a/README
+++ b/README
@@ -1,10 +1,10 @@
#################################
-__ __ _ _ __ _ _ _
-\ \/ /___ _ __ | || | / /_ _ _ _ __ ___| |_ __ _| |__ | | ___
- \ // _ \ '_ \ | || |_| '_ \ _____| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
- / \ __/ | | | |__ _| (_) |_____| |_| | | | \__ \ || (_| | |_) | | __/
-/_/\_\___|_| |_| |_|(_)___/ \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
-
+__ __ _ _ __
+\ \/ /___ _ __ | || | / /_ _ __ ___
+ \ // _ \ '_ \ | || |_| '_ \ _____| '__/ __|
+ / \ __/ | | | |__ _| (_) |_____| | | (__
+/_/\_\___|_| |_| |_|(_)___/ |_| \___|
+
#################################
http://www.xen.org/
diff --git a/xen/Makefile b/xen/Makefile
index 6305880..6088c9d 100644
--- a/xen/Makefile
+++ b/xen/Makefile
@@ -2,7 +2,7 @@
# All other places this is stored (eg. compile.h) should be autogenerated.
export XEN_VERSION = 4
export XEN_SUBVERSION = 6
-export XEN_EXTRAVERSION ?= -unstable$(XEN_VENDORVERSION)
+export XEN_EXTRAVERSION ?= .0-rc$(XEN_VENDORVERSION)
export XEN_FULLVERSION = $(XEN_VERSION).$(XEN_SUBVERSION)$(XEN_EXTRAVERSION)
-include xen-version
--
1.7.10.4
next prev parent reply other threads:[~2015-08-11 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 14:09 [PATCH for-4.6 URGENT 0/4] Prepare for RC1 Ian Jackson
2015-08-11 14:09 ` [PATCH 1/4] tools: Update sonames for 4.6 RCs Ian Jackson
2015-08-11 14:15 ` Wei Liu
2015-08-11 14:24 ` Ian Jackson
2015-08-11 14:27 ` [PATCH v2 " Ian Jackson
2015-08-11 14:28 ` Wei Liu
2015-08-11 14:09 ` Ian Jackson [this message]
2015-08-11 14:15 ` [PATCH 2/4] Update version to Xen 4.6 RC Wei Liu
2015-08-11 14:32 ` Ian Campbell
2015-08-11 14:09 ` [PATCH 3/4] Update QEMU_TRADITIONAL_REVISION for 4.6 RC1 Ian Jackson
2015-08-11 14:15 ` Wei Liu
2015-08-11 14:09 ` [PATCH 4/4] Update QEMU_UPSTREAM_REVISION " Ian Jackson
2015-08-11 14:15 ` 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:
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=1439302160-24633-3-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=jbeulich@suse.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xensource.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 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).