From: George Dunlap <george.dunlap@eu.citrix.com>
To: Meng Xu <xumengpanda@gmail.com>,
Dario Faggioli <dario.faggioli@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel <xen-devel@lists.xen.org>,
Meng Xu <mengxu@cis.upenn.edu>, Jan Beulich <jbeulich@suse.com>,
Chong Li <lichong659@gmail.com>,
Dagaen Golomb <dgolomb@seas.upenn.edu>
Subject: Re: [PATCH v2 for Xen 4.6 0/4] Enabling XL to set per-VCPU parameters of a domain for RTDS scheduler
Date: Mon, 1 Jun 2015 09:36:36 +0100 [thread overview]
Message-ID: <556C1994.4090101@eu.citrix.com> (raw)
In-Reply-To: <CAENZ-+mf8tv7cDuhaHN6SesK-FkwTnQM3zC1VFVwFDQkewvqsg@mail.gmail.com>
On 05/29/2015 03:40 PM, Meng Xu wrote:
> 2015-05-29 4:15 GMT-07:00 Dario Faggioli <dario.faggioli@citrix.com>:
>
>> 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@blah.blah>" 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@eu.citrix.com>
---
CC: Ian Campbell <ian.campbell@citrix.com>
CC: Wei Liu <wei.liu@citrix.com>
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@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-06-01 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 23:59 [PATCH v2 for Xen 4.6 0/4] Enabling XL to set per-VCPU parameters of a domain for RTDS scheduler Chong Li
2015-05-26 8:59 ` Ian Campbell
2015-05-29 11:15 ` Dario Faggioli
2015-05-29 14:40 ` Meng Xu
2015-06-01 8:36 ` George Dunlap [this message]
2015-06-01 8:48 ` Ian Campbell
2015-06-01 8:50 ` George Dunlap
2015-06-01 8:57 ` Ian Campbell
2015-06-01 8:58 ` Jan Beulich
2015-06-01 9:06 ` Andrew Cooper
2015-06-01 9:20 ` George Dunlap
2015-06-01 9:44 ` Ian Campbell
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=556C1994.4090101@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=dgolomb@seas.upenn.edu \
--cc=ian.campbell@citrix.com \
--cc=jbeulich@suse.com \
--cc=lichong659@gmail.com \
--cc=mengxu@cis.upenn.edu \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xumengpanda@gmail.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 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.