All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Julien Grall <julien@xen.org>, Wei Liu <wl@xen.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Jan Beulich <jbeulich@suse.com>
Subject: [Xen-devel] [PATCH 4/9] release technician checklist: Reformat Config.mk changes
Date: Fri, 29 Nov 2019 15:04:11 +0000	[thread overview]
Message-ID: <20191129150416.4944-5-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <20191129150416.4944-1-ian.jackson@eu.citrix.com>

One per line is a lot easier to read.

Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
---
 docs/process/release-technician-checklist.txt | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/docs/process/release-technician-checklist.txt b/docs/process/release-technician-checklist.txt
index 5dd85dbc40..ebf338c9d4 100644
--- a/docs/process/release-technician-checklist.txt
+++ b/docs/process/release-technician-checklist.txt
@@ -49,7 +49,10 @@ 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)
-* change xen-unstable Config.mk (QEMU_UPSTREAM_REVISION, QEMU_TRADITIONAL_REVISION, MINIOS_UPSTREAM_REVISION)
+* change xen-unstable Config.mk
+#   QEMU_UPSTREAM_REVISION,
+#   QEMU_TRADITIONAL_REVISION
+#   MINIOS_UPSTREAM_REVISION
 * change SUPPORT.md heading version number; -unstable or -rc tag
 *     (empty in stable branches after .0 release).
 *     insert correct version number in release-notes link
-- 
2.11.0


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2019-11-29 15:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 15:04 [Xen-devel] [PATCH 0/9] Process docs updates Ian Jackson
2019-11-29 15:04 ` [Xen-devel] [PATCH 1/9] branching checklist: drop some hg tag runes Ian Jackson
2019-11-29 15:04 ` [Xen-devel] [PATCH 2/9] branching checklist: Say perhaps no Config.mk changes needed Ian Jackson
2019-11-29 15:04 ` [Xen-devel] [PATCH 3/9] branching checklist: More detailed instructions re MAINTAINERS Ian Jackson
2019-11-29 15:04 ` Ian Jackson [this message]
2019-11-29 15:04 ` [Xen-devel] [PATCH 5/9] release technician checklist: More explicit XEN_EXTRAVERSION Ian Jackson
2019-11-29 15:16   ` Jan Beulich
2019-11-29 15:04 ` [Xen-devel] [PATCH 6/9] docs/process: Fix minor error in formatting Ian Jackson
2019-11-29 15:04 ` [Xen-devel] [PATCH 7/9] docs/process: Mention .Z-pre versions Ian Jackson
2019-11-29 15:04 ` [Xen-devel] [PATCH 8/9] docs/process: Notify release manager, rather than editing website Ian Jackson
2019-11-29 15:04 ` [Xen-devel] [PATCH 9/9] docs/process: Move MAINTAINERS update for stable to .0 release Ian Jackson

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=20191129150416.4944-5-ian.jackson@eu.citrix.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=konrad.wilk@oracle.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.