DPDK CI discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 170] Send separate emails to users instead of CCing everyone
Date: Tue, 18 Dec 2018 15:48:30 +0000	[thread overview]
Message-ID: <bug-170-149@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=170

            Bug ID: 170
           Summary: Send separate emails to users instead of CCing
                    everyone
           Product: lab
           Version: unspecified
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: enhancement
          Priority: Normal
         Component: job scripts
          Assignee: ci@dpdk.org
          Reporter: jplsek@iol.unh.edu
                CC: jplsek@iol.unh.edu
  Target Milestone: ---

When results are emailed, all subscriptions are included in the same email.

We either need to just BCC everyone, or send a separate email to each user.

I'm assuming the BCC would be the easiest.

(Originally created 09/Nov/18 1:27 PM)

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2018-12-18 15:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-170-149@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=ci@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).