From: "Jan Beulich" <JBeulich@suse.com>
To: Ian Jackson <ian.jackson@eu.citrix.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>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 0/4] misc/release-checklist: Updates prompted by recent release
Date: Thu, 09 Mar 2017 08:53:16 -0700 [thread overview]
Message-ID: <58C1887C0200007800141B48@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1489072767-21441-1-git-send-email-ian.jackson@eu.citrix.com>
>>> On 09.03.17 at 16:19, <ian.jackson@eu.citrix.com> wrote:
> 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.
No objections; I've just sent a few minor comments.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-03-09 15:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 15:19 [PATCH 0/4] misc/release-checklist: Updates prompted by recent release Ian Jackson
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 ` Jan Beulich [this message]
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=58C1887C0200007800141B48@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--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.