From: Jan Beulich <jbeulich@suse.com>
To: Julien Grall <julien@xen.org>
Cc: Henry.Wang@arm.com, Julien Grall <jgrall@amazon.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 3/3] Update Xen version to 4.17-rc
Date: Fri, 7 Oct 2022 13:06:24 +0200 [thread overview]
Message-ID: <304f4bbf-3598-2f42-5cee-83e58c1909cc@suse.com> (raw)
In-Reply-To: <20221007091341.58542-4-julien@xen.org>
On 07.10.2022 11:13, Julien Grall wrote:
> From: Julien Grall <jgrall@amazon.com>
>
> Signed-off-by: Julien Grall <jgrall@amazon.com>
> ---
> README | 16 ++++++++--------
> SUPPORT.md | 2 +-
> xen/Makefile | 2 +-
> 3 files changed, 10 insertions(+), 10 deletions(-)
I assume CHANGELOG.md is then going to be updated only once for the actual
release? (Not that I think that the -rc is relevant to have there, but the
version could as well be changed to 4.17.0 already now.)
Jan
next prev parent reply other threads:[~2022-10-07 11:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 9:13 [PATCH 0/3] Prepare the tree for 4.17 RC Julien Grall
2022-10-07 9:13 ` [PATCH 1/3] process/release-technician-checklist: Explain how the banner in README is generated Julien Grall
2022-10-07 9:42 ` Henry Wang
2022-10-07 9:42 ` Juergen Gross
2022-10-07 11:02 ` Jan Beulich
2022-10-07 13:20 ` Julien Grall
2022-10-07 9:13 ` [PATCH 2/3] Config.mk pin QEMU_UPSTREAM_REVISION (prep for Xen 4.17 RC1) Julien Grall
2022-10-07 9:45 ` Henry Wang
2022-10-07 9:13 ` [PATCH 3/3] Update Xen version to 4.17-rc Julien Grall
2022-10-07 9:51 ` Henry Wang
2022-10-07 9:56 ` Julien Grall
2022-10-07 9:58 ` Henry Wang
2022-10-07 11:06 ` Jan Beulich [this message]
2022-10-07 13:26 ` Julien Grall
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=304f4bbf-3598-2f42-5cee-83e58c1909cc@suse.com \
--to=jbeulich@suse.com \
--cc=Henry.Wang@arm.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jgrall@amazon.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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 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.