All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien@xen.org>
To: Jan Beulich <jbeulich@suse.com>
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 1/3] process/release-technician-checklist: Explain how the banner in README is generated
Date: Fri, 7 Oct 2022 14:20:27 +0100	[thread overview]
Message-ID: <e5314094-862e-9022-3707-7e308e9f2e67@xen.org> (raw)
In-Reply-To: <60eda03c-9e40-2a99-dfe5-7ba1407961ad@suse.com>

Hi Jan,

On 07/10/2022 12:02, Jan Beulich wrote:
> On 07.10.2022 11:13, Julien Grall wrote:
>> --- a/docs/process/release-technician-checklist.txt
>> +++ b/docs/process/release-technician-checklist.txt
>> @@ -49,6 +49,7 @@ t=RELEASE-$r
>>   * consider bumping sonames of shlibs
>>   
>>   * change xen-unstable README (should say "Xen 4.5" in releases and on stable branches, "Xen 4.5-unstable" on unstable)
> 
> This line may also want updating, to include the 4.5-rc case as well.

Good point. I will respin this patch.

Cheers,

> 
> Jan
> 
>> +*   The banner is generated using figlet
>>   * change xen-unstable Config.mk
>>   #   QEMU_UPSTREAM_REVISION,
>>   #   QEMU_TRADITIONAL_REVISION
> 

-- 
Julien Grall


  reply	other threads:[~2022-10-07 13:20 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 [this message]
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
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=e5314094-862e-9022-3707-7e308e9f2e67@xen.org \
    --to=julien@xen.org \
    --cc=Henry.Wang@arm.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgrall@amazon.com \
    --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.