patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: stable@dpdk.org
Cc: thomas@monjalon.net, ktraynor@redhat.com, yskoh@mellanox.com,
	christian.ehrhardt@canonical.com
Subject: [dpdk-stable] [PATCH stable-scripts 2/2] 3-request-backport: use BCC for stable@dpdk.org to bypass filters
Date: Sun, 24 Feb 2019 12:24:44 +0000	[thread overview]
Message-ID: <20190224122444.24085-2-bluca@debian.org> (raw)
In-Reply-To: <20190224122444.24085-1-bluca@debian.org>

It has been reported that the backport request mail gets caught by filters
and thus many developers do not see it.
Use BCC instead of CC for the list, and use it in Reply-To, to bypass the
filters.

Signed-off-by: Luca Boccassi <bluca@debian.org>
---
 3-request-backport | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/3-request-backport b/3-request-backport
index 8bdf2a4..62f6bf3 100755
--- a/3-request-backport
+++ b/3-request-backport
@@ -43,7 +43,8 @@ get_cc_list()
 	rm $cc_list
 }
 
-echo "To: dpdk stable <stable@dpdk.org>"
+echo "Bcc: dpdk stable <stable@dpdk.org>"
+echo "Reply-To: dpdk stable <stable@dpdk.org>"
 get_cc_list
 echo "Subject: please help backporting some patches to $(stable_or_lts) release $stable_release"
 
-- 
2.20.1

  reply	other threads:[~2019-02-24 12:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24 12:24 [dpdk-stable] [PATCH stable-scripts 1/2] 3-request-backport: suppress pushd/popd output Luca Boccassi
2019-02-24 12:24 ` Luca Boccassi [this message]
2019-03-04 19:13   ` [dpdk-stable] [PATCH stable-scripts 2/2] 3-request-backport: use BCC for stable@dpdk.org to bypass filters Yongseok Koh
2019-03-04 19:13 ` [dpdk-stable] [PATCH stable-scripts 1/2] 3-request-backport: suppress pushd/popd output Yongseok Koh

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=20190224122444.24085-2-bluca@debian.org \
    --to=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=ktraynor@redhat.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=yskoh@mellanox.com \
    /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).