All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org,
	Lars Kurth <lars.kurth@citrix.com>,
	keir@xen.org, stefano.stabellini@eu.citrix.com
Subject: Re: [OSSTEST PATCH 1/4] Email reports: Sort out recipients and Reply-to
Date: Wed, 8 Jul 2015 16:27:26 +0100	[thread overview]
Message-ID: <1436369246.23508.69.camel@citrix.com> (raw)
In-Reply-To: <1436368876-23964-1-git-send-email-ian.jackson@eu.citrix.com>

On Wed, 2015-07-08 at 16:21 +0100, Ian Jackson wrote:
> No longer send reports, or copies, to named individuals.  Instead,
> send all output to 1. appropriate development mailing lists 2. the new
> osstest-admin@xenproject administrator alias, and 3. Bcc the new
> osstest-output list.
> 
> Bisection progress emails go only to osstest-output.  In this case we
> provide a Reply-To.
> 
> After this patch goes live, people interested in bisection progress
> emails will find them in osstest-output.  (There are a lot of these.)
> Such people can also subscribe to osstest-output and get copies of
> only the main test reports and then use recipient-side filtering to
> see the ones they find interesting.
> 
> (Configurations for `adhoc' and `play' runs remain unchanged and still
> have a tendency to refer to my personal address @citrix.)
> 
> Deployment notes:
> 
> Keir and Stefano will no longer receive automatic CCs of certain
> reports, and should subscribe to the osstest-output list, with
> appropriate filtering, if they care.
> 
> The new osstest-output list has (I think) been configured to accept
> the BCCs.
> 
> My personal chiark mail-to-news gateway has already been subscribed to
> osstest-output.
> 
> One substantial change is that the osstest admin now gets copies of
> each final bisection failure.
> 
> Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
> CC: keir@xen.org
> CC: stefano.stabellini@eu.citrix.com
> CC: Lars Kurth <lars.kurth@citrix.com>

Acked-by: Ian Campbell <ian.campbell@citrix.com>

  parent reply	other threads:[~2015-07-08 15:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 15:21 [OSSTEST PATCH 1/4] Email reports: Sort out recipients and Reply-to Ian Jackson
2015-07-08 15:21 ` [OSSTEST PATCH 2/4] Reporting: Make HTML reports for bisection flights too Ian Jackson
2015-07-08 15:28   ` Ian Campbell
2015-07-08 15:21 ` [OSSTEST PATCH 3/4] mg-branch-setup: Get the direction of the tree-bisect link right Ian Jackson
2015-07-08 15:28   ` Ian Campbell
2015-07-08 15:21 ` [OSSTEST PATCH 4/4] JobDB/Executive: Improve an internal `die' error Ian Jackson
2015-07-08 15:29   ` Ian Campbell
2015-07-08 15:27 ` Ian Campbell [this message]
2015-07-08 15:40   ` [OSSTEST PATCH 1/4] Email reports: Sort out recipients and Reply-to Ian Jackson

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=1436369246.23508.69.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=lars.kurth@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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.