All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@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 09:35:20 +0100	[thread overview]
Message-ID: <1435826120.21469.307.camel@citrix.com> (raw)
In-Reply-To: <5593BE34.20407@citrix.com>

On Wed, 2015-07-01 at 11:17 +0100, Julien Grall wrote:
> As suggested by Wei on the top of his mail [1], can you please CC only
> relevant people and avoid to reply all?

It seems that many people are unable to follow these simple
instructions.

Wei, perhaps you could stop CCing people who inappropriately do not trim
their quotes or the CC list in the future. If they cannot do us the
courtesy of doing so I don't see why they should receive a courtesy copy
of the status mail.

A somewhat less aggressive approach might be to use Bcc instead Cc for
the bulk of people (i.e. anyone who needn't be cc-d on every reply). The
failure case of someone who cannot read simple instructions then becomes
a lack of CCs rather than a plethora of unwanted Ccs.

Ian.

> 
> Many thanks,
> 
> [1] (Note, please trim your quotes when replying, and also trim the CC
> list if
> necessary. You might also consider changing the subject line of your
> reply to
> "Status of FOO (Was: Xen 4.6 Development Update (X months reminder)")
> 
> On 01/07/15 07:12, Chen, Tiejun wrote:
> >>
> >> *  RMRR fix (fair)
> >>     RFC posted
> > 
> > Wei,
> > 
> > I think this should be ok or good based on current status, and also
> > should remove "RFC" here.
> > 
> > Thanks
> > Tiejun
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
> 
> 

  reply	other threads:[~2015-07-02  8:35 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 [this message]
2015-07-02  8:51       ` Razvan Cojocaru
2015-07-02 10:32         ` Dario Faggioli
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=1435826120.21469.307.camel@citrix.com \
    --to=ian.campbell@citrix.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.