All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble)
Date: Thu, 2 Jul 2015 12:32:38 +0200	[thread overview]
Message-ID: <1435833158.25170.448.camel@citrix.com> (raw)
In-Reply-To: <5594FB8E.6000305@bitdefender.com>


[-- Attachment #1.1: Type: text/plain, Size: 1777 bytes --]

On Thu, 2015-07-02 at 11:51 +0300, Razvan Cojocaru wrote:
> On 07/02/2015 11:35 AM, Ian Campbell wrote:
> > It seems that many people are unable to follow these simple
> > instructions.
> 
> The quotes part is obvious (and not that many people have ommited to do
> that), but to be honest I haven't been clear on who is supposed to be in
> the trimmed CC list: the maintainers of the code I'm touching with my
> series and Wei? 
>
Exactly.

It's the 'interested parties' that should be Cc-ed, which, 99% of the
times, is exactly what you just said:
 - the maintainers because, well, they are the maintainers, they know
   the code, they most likely know your series and will be able to
   engage in a conversation on whether the estimation is correct or not;
 - the release manager, since we're discussing release;
 - there might me more people, such as, people that have been involved
   in the review process, despite not being maintainers, or... no,
   that's all that comes to my mind.

So, trim to such a set, and you'll make most of the people happy, I bet.

> There doesn't seem to be a clear rule about who should
> be replied to (or maybe there is and I've missed it? If so, could you
> please point it out?). Maybe clearing this up could help with this
> problem in the future.
> 
I think it was pretty obvious. I guess it would not harm to add a line
making this crystal clear in the mail, but it's Wei's call to judge
whether that is really necessary.

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-07-02 10:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 11:16 Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) wei.liu2
2015-06-26 11:27 ` Status of VM event patches (Was: Re: Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble)) Razvan Cojocaru
2015-06-26 11:32   ` Julien Grall
2015-06-26 11:34     ` Razvan Cojocaru
2015-06-26 12:06 ` Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) Vitaly Kuznetsov
2015-07-06 15:03   ` Wei Liu
2015-06-26 13:32 ` Jan Beulich
2015-06-26 13:49 ` gnttab scalability and ticket locks status David Vrabel
2015-06-26 14:30   ` Ian Campbell
2015-06-26 15:38     ` Jan Beulich
2015-06-26 13:50 ` Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) Andrew Cooper
2015-06-26 14:45 ` Daniel Kiper
2015-06-26 15:23 ` Status of VM event patches (Was: Re: Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble)) Razvan Cojocaru
2015-07-06 15:00   ` Wei Liu
2015-07-06 15:05     ` Razvan Cojocaru
2015-06-26 16:17 ` Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) Julien Grall
2015-06-30  2:30 ` Status of COLO (Was: Xen 4.6 Development Update) Yang Hongyang
2015-07-01  6:12 ` Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) Chen, Tiejun
2015-07-01 10:17   ` Julien Grall
2015-07-02  8:35     ` Ian Campbell
2015-07-02  8:51       ` Razvan Cojocaru
2015-07-02 10:32         ` Dario Faggioli [this message]
2015-07-01 10:01 ` Yu, Zhang

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=1435833158.25170.448.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=rcojocaru@bitdefender.com \
    --cc=wei.liu2@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.