From: Don Slutz <dslutz@verizon.com>
To: Jan Beulich <JBeulich@suse.com>, Don Slutz <dslutz@verizon.com>
Cc: Keir Fraser <keir@xen.org>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [BUGFIX][PATCH v2 0/5] gdbsx: fix 3 bugs
Date: Wed, 08 Jan 2014 09:43:52 -0500 [thread overview]
Message-ID: <52CD6428.9060102@terremark.com> (raw)
In-Reply-To: <52CD1A5B02000078001116AD@nat28.tlf.novell.com>
On 01/08/14 03:28, Jan Beulich wrote:
>>>> On 08.01.14 at 01:25, Don Slutz <dslutz@verizon.com> wrote:
>> Release manager requests:
>> patch 1 and 3 are optional for 4.4.0.
>> patch 2 should be in 4.4.0
>> patch 4 and 5 would be good to be in 4.4.0
> Which clearly shows that the series is badly ordered: You shouldn't
> expect committers to know (or even have to guess) that applying
> later patches without earlier ones is okay. I.e. if you think that
> leaving out part of the series for 4.4 is fine, you should place the
> required ones first, the optional ones second, and the 4.5 ones
> last. Or, if the patches are in fact independent, another option
> would be to not send the patches as a series in the first place.
If this was not real close to the release date, I would not have added this information. Clearly the way I wrote it is not the way it should be expressed. Thanks for you help, I will try to do that ordering in the future.
-Don Slutz
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-01-08 14:43 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 0:25 [BUGFIX][PATCH v2 0/5] gdbsx: fix 3 bugs Don Slutz
2014-01-08 0:25 ` [PATCH v2 1/5] Add Emacs local variables to source files Don Slutz
2014-01-08 1:16 ` Mukesh Rathor
2014-01-08 1:27 ` Andrew Cooper
2014-01-08 9:51 ` Ian Campbell
2014-01-08 15:58 ` Ian Campbell
2014-01-08 0:25 ` [BUGFIX][PATCH v2 2/5] dbg_rw_guest_mem: need to call put_gfn in error path Don Slutz
2014-01-08 0:55 ` Andrew Cooper
2014-01-08 1:06 ` Don Slutz
2014-01-08 1:15 ` Andrew Cooper
2014-01-08 1:14 ` Mukesh Rathor
2014-01-08 1:44 ` Mukesh Rathor
2014-01-08 2:30 ` Andrew Cooper
2014-01-08 2:44 ` Mukesh Rathor
2014-01-08 10:40 ` Ian Campbell
2014-01-08 14:01 ` Don Slutz
2014-01-08 8:36 ` Jan Beulich
2014-01-08 13:48 ` Don Slutz
2014-01-08 0:25 ` [PATCH v2 3/5] dbg_rw_guest_mem: Conditionally enable debug log output Don Slutz
2014-01-08 1:38 ` Mukesh Rathor
2014-01-08 10:38 ` Ian Campbell
2014-01-08 14:28 ` Don Slutz
2014-01-08 16:47 ` Ian Campbell
2014-01-08 17:04 ` Tim Deegan
2014-01-08 17:44 ` Ian Campbell
2014-01-08 18:10 ` Tim Deegan
2014-01-09 8:41 ` Ian Campbell
2014-01-09 10:32 ` Tim Deegan
2014-01-09 0:38 ` Mukesh Rathor
2014-01-09 9:59 ` Ian Campbell
2014-01-09 16:08 ` Don Slutz
2014-01-09 16:30 ` Jan Beulich
2014-01-09 17:56 ` Don Slutz
2014-01-10 17:13 ` Ian Campbell
2014-01-10 21:15 ` Don Slutz
2014-01-10 22:08 ` [PATCH v3 " Don Slutz
2014-01-10 1:54 ` [PATCH v2 " Mukesh Rathor
2014-01-08 0:25 ` [BUGFIX][PATCH v2 4/5] xg_read_mem: Report on error Don Slutz
2014-01-08 1:16 ` Mukesh Rathor
2014-01-08 0:25 ` [BUGFIX][PATCH v2 5/5] xg_main: If XEN_DOMCTL_gdbsx_guestmemio fails then force error Don Slutz
2014-01-08 1:11 ` Mukesh Rathor
2014-01-08 10:35 ` Ian Campbell
2014-01-08 14:39 ` Don Slutz
2014-01-08 8:28 ` [BUGFIX][PATCH v2 0/5] gdbsx: fix 3 bugs Jan Beulich
2014-01-08 14:43 ` Don Slutz [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=52CD6428.9060102@terremark.com \
--to=dslutz@verizon.com \
--cc=JBeulich@suse.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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.