From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>, Jan Beulich <jbeulich@suse.com>
Subject: [PATCH 0/4] misc/release-checklist: Updates prompted by recent release
Date: Thu, 9 Mar 2017 15:19:23 +0000 [thread overview]
Message-ID: <1489072767-21441-1-git-send-email-ian.jackson@eu.citrix.com> (raw)
When doing the recent stable release branches, I tripped over some
deficiencies in these checklists. And, now that they are in git, we
can much more safely throw away a lot of ancient stuff.
Please shout if you have any objections. I hope to push this today.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-03-09 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 15:19 Ian Jackson [this message]
2017-03-09 15:19 ` [PATCH 1/4] misc/release-checklist: Remove clearly-obsolete stuff Ian Jackson
2017-03-09 15:19 ` [PATCH 2/4] misc/release-checklist: Remove pre-4.3 tarball target instructions Ian Jackson
2017-03-09 15:50 ` Jan Beulich
2017-03-09 15:53 ` Ian Jackson
2017-03-09 15:55 ` Jan Beulich
2017-03-09 15:19 ` [PATCH 3/4] misc/release-checklist: Split out branching-checklist.txt Ian Jackson
2017-03-09 15:52 ` Jan Beulich
2017-03-09 15:54 ` Ian Jackson
2017-03-09 15:19 ` [PATCH 4/4] misc/branching-checklist: Call mg-branch-setup in Cambridge too Ian Jackson
2017-03-09 15:53 ` [PATCH 0/4] misc/release-checklist: Updates prompted by recent release Jan Beulich
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=1489072767-21441-1-git-send-email-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=sstabellini@kernel.org \
--cc=tim@xen.org \
--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).