[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v2 00/10] Intel Processor Trace virtulization enabling

> >> -----Original Message-----
> >> From: Julien Grall [mailto:julien.grall@xxxxxxx]
> >> Sent: Wednesday, May 30, 2018 11:15 PM
> >> To: Kang, Luwei <luwei.kang@xxxxxxxxx>; xen-devel@xxxxxxxxxxxxx
> >> Cc: andrew.cooper3@xxxxxxxxxx; George.Dunlap@xxxxxxxxxxxxx;
> >> ian.jackson@xxxxxxxxxxxxx; jbeulich@xxxxxxxx; konrad.wilk@xxxxxxxxxx;
> >> sstabellini@xxxxxxxxxx; tim@xxxxxxx; wei.liu2@xxxxxxxxxx; Nakajima,
> >> Jun <jun.nakajima@xxxxxxxxx>; Tian, Kevin <kevin.tian@xxxxxxxxx>
> >> Subject: Re: [PATCH v2 00/10] Intel Processor Trace virtulization
> >> enabling
> >>
> >> Hi,
> >>
> >> Can you please avoid CC everyone on each patch? You can use
> >> scripts/get_maintainers.pl on each patch to see who is required to be CCed.
> >
> > OK, get it. I use script/get_maintainers.pl to get the people who need to 
> > be CC and indeed different patch may include different
> peoples. If somebody  just receive one patch of this patch set may feel a 
> little strange and don't understand the context. So I CC all
> the peoples who is mentioned in this patch set.
> That's usually why I CC everyone on the cover letter. Then for each patch I 
> CC only the necessary person.
> This avoids maintainers to have to look for what they should review/ack.

Get it. This is a good way to me.  Thanks.

Luwei Kang
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.