From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Oleksii Kurochko" <oleksii.kurochko@gmail.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 2/2] Update Xen version to 4.20-rc
Date: Thu, 9 Jan 2025 15:46:47 +0000 [thread overview]
Message-ID: <c7eeaa80-a4bd-457f-824e-accd23c2f471@citrix.com> (raw)
In-Reply-To: <67278014-8208-48f2-92ba-7b843a0d373b@suse.com>
On 09/01/2025 3:44 pm, Jan Beulich wrote:
> On 09.01.2025 16:39, Andrew Cooper wrote:
>> --- a/README
>> +++ b/README
>> @@ -1,11 +1,11 @@
>> -############################################################
>> -__ __ _ _ _
>> -\ \/ /___ _ __ _ _ _ __ ___| |_ __ _| |__ | | ___
>> - \ // _ \ '_ \ _____| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
>> - / \ __/ | | |_____| |_| | | | \__ \ || (_| | |_) | | __/
>> -/_/\_\___|_| |_| \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
>> -
>> -############################################################
>> +#####################################################
>> +__ __ _ _ ____ ___
>> +\ \/ /___ _ __ | || | |___ \ / _ \ _ __ ___
>> + \ // _ \ '_ \ | || |_ __) | | | |_____| '__/ __|
>> + / \ __/ | | | |__ _| / __/| |_| |_____| | | (__
>> +/_/\_\___|_| |_| |_|(_)_____|\___/ |_| \___|
>> +
>> +#####################################################
>>
>> https://www.xen.org/
>>
>> --- a/SUPPORT.md
>> +++ b/SUPPORT.md
>> @@ -9,7 +9,7 @@ for the definitions of the support status levels etc.
>>
>> # Release Support
>>
>> - Xen-Version: 4.20-unstable
>> + Xen-Version: 4.20-rc
>> Initial-Release: n/a
>> Supported-Until: TBD
>> Security-Support-Until: Unreleased - not yet security-supported
>> --- a/xen/Makefile
>> +++ b/xen/Makefile
>> @@ -6,7 +6,7 @@ this-makefile := $(call lastword,$(MAKEFILE_LIST))
>> # All other places this is stored (eg. compile.h) should be autogenerated.
>> export XEN_VERSION = 4
>> export XEN_SUBVERSION = 20
>> -export XEN_EXTRAVERSION ?= -unstable$(XEN_VENDORVERSION)
>> +export XEN_EXTRAVERSION ?= .0-rc$(XEN_VENDORVERSION)
> Since we'd been there before I take it the .0 in here (which isn't in the
> changes to the other two files) is deliberate now? Clearly I continue to
> think it shouldn't be put there together with -rc.
Oh, that's because I cribbed this by looking at the recent releases.
The documentation leaves ~everything to be desired...
I can drop the .0 here, although I shan't repost just for that.
~Andrew
next prev parent reply other threads:[~2025-01-09 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 15:39 [PATCH for-4.20 0/2] Prep for 4.20-rc1 Andrew Cooper
2025-01-09 15:39 ` [PATCH 1/2] Config.mk: Pin QEMU_UPSTREAM_REVISION Andrew Cooper
2025-01-09 15:53 ` Anthony PERARD
2025-01-09 15:39 ` [PATCH 2/2] Update Xen version to 4.20-rc Andrew Cooper
2025-01-09 15:44 ` Jan Beulich
2025-01-09 15:46 ` Andrew Cooper [this message]
2025-01-09 15:53 ` Jan Beulich
2025-01-10 17:16 ` Andrew Cooper
2025-01-09 15:55 ` Oleksii Kurochko
2025-01-09 15:58 ` [PATCH for-4.20 0/2] Prep for 4.20-rc1 Oleksii Kurochko
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=c7eeaa80-a4bd-457f-824e-accd23c2f471@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=oleksii.kurochko@gmail.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--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 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).