[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v2 for Xen 4.6 0/4] Enabling XL to set per-VCPU parameters of a domain for RTDS scheduler
On 05/29/2015 03:40 PM, Meng Xu wrote: > 2015-05-29 4:15 GMT-07:00 Dario Faggioli <dario.faggioli@xxxxxxxxxx>: > >> On Tue, 2015-05-26 at 09:59 +0100, Ian Campbell wrote: >>> On Mon, 2015-05-25 at 18:59 -0500, Chong Li wrote: >>> >>> This series arrived in my mailbox as 5 distinct mails. >>> >>> Please use git send-email such that the mails arrive as a single email >>> thread (i.e. each mail as a reply to the previous or to the 0th mail) or >>> arrange for the same thing by hand (I highly recommend using git >>> send-email though) >>> >> Indeed. >> >> BTW, Chong, v1 was threaded ok, so maybe did something different this >> time when sending the patches. If yes, just don't! :-) >> > > > âI think that's because Chong wanted to send different patches in this > patch set to different maintainers. (For example, we don't want to spam > Jan's folder with xl, libxl patch. :-) ) > > Is it ok to use "git send-email --reply-to" to attach all four patches to > the cover letter (that is this email thread) of the patch set? So two git features: * If you write "CC: Name <address@xxxxxxxxx>" in your commit message, git send-email will CC that person *just for that commit* * Anything in the description under a line starting with "---" will be discarded So you can write your message like this: 8<-------------------------------------- libxl: A one-line example. This is just an example commit. Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx> --- CC: Ian Campbell <ian.campbell@xxxxxxxxxx> CC: Wei Liu <wei.liu@xxxxxxxxxx> 8<-------------------------------------- And when you do git-send-email, it will automatically CC Ian and Wei (and only them) for this patch. -George _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |