All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	xen-devel <xen-devel@lists.xen.org>,
	Meng Xu <xumengpanda@gmail.com>, 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:50:16 +0100	[thread overview]
Message-ID: <556C1CC8.10301@eu.citrix.com> (raw)
In-Reply-To: <1433148506.15036.78.camel@citrix.com>

On 06/01/2015 09:48 AM, Ian Campbell wrote:
> On Mon, 2015-06-01 at 09:36 +0100, George Dunlap wrote:
>> Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
>> ---
>> CC: Ian Campbell <ian.campbell@citrix.com>
>> CC: Wei Liu <wei.liu@citrix.com>
> 
> Most people put the Cc about the cut (---) which is fine too. It means
> the history ends up recording who was copied on the patch, which isn't
> necessarily a bad thing.

Right -- I would have thought that was useless information cluttering up
the history, but I can see how it might actually be useful.  Should I
start putting my CC's above the ---? :-)

 -George

  reply	other threads:[~2015-06-01  8:50 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
2015-06-01  8:48         ` Ian Campbell
2015-06-01  8:50           ` George Dunlap [this message]
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=556C1CC8.10301@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.