From: George Dunlap <george.dunlap@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: Lars Kurth <lars.kurth@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>, Wei Liu <wl@xen.org>,
Konrad Wilk <konrad.wilk@oracle.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>, Jan Beulich <jbeulich@suse.com>,
Ian Jackson <ian.jackson@citrix.com>
Subject: Re: [Xen-devel] [PATCH] MAINTAINERS: Add explicit check-in policy section
Date: Tue, 7 Jan 2020 12:05:16 +0000 [thread overview]
Message-ID: <50c9693d-91a4-31b0-c441-a02a5a19f662@citrix.com> (raw)
In-Reply-To: <20200107120320.222364-1-george.dunlap@citrix.com>
On 1/7/20 12:03 PM, George Dunlap wrote:
> v2:
> - Modify "sufficient time" to "sufficient time and/or warning".
> - Add a comment explicitly stating that there are exceptions.
> - Move some of the alternate proposals into the changelog itself
Sorry, this should obviously have 'v2' in the subject.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-01-07 12:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 12:03 [Xen-devel] [PATCH] MAINTAINERS: Add explicit check-in policy section George Dunlap
2020-01-07 12:05 ` George Dunlap [this message]
2020-01-07 13:05 ` Jan Beulich
2020-01-07 16:17 ` George Dunlap
2020-01-07 16:44 ` Jan Beulich
2020-01-13 15:07 ` George Dunlap
-- strict thread matches above, loose matches on Subject: below --
2019-05-08 11:39 George Dunlap
2019-05-08 11:39 ` George Dunlap
2019-05-08 11:59 ` Juergen Gross
2019-05-08 11:59 ` Juergen Gross
2019-05-08 13:45 ` George Dunlap
2019-05-08 13:45 ` George Dunlap
2019-05-09 11:05 ` Ian Jackson
2019-05-09 11:05 ` Ian Jackson
2019-05-09 11:36 ` Jan Beulich
2019-05-09 11:36 ` Jan Beulich
2019-05-08 13:49 ` Jan Beulich
2019-05-08 13:49 ` Jan Beulich
2019-05-08 15:32 ` Stefano Stabellini
2019-05-08 15:32 ` Stefano Stabellini
2019-05-09 11:16 ` Ian Jackson
2019-05-09 11:16 ` Ian Jackson
2019-05-09 11:45 ` George Dunlap
2019-05-09 11:45 ` George Dunlap
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=50c9693d-91a4-31b0-c441-a02a5a19f662@citrix.com \
--to=george.dunlap@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=lars.kurth@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.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.