From: Tino Calancha <tino.calancha@gmail.com>
To: 28833@debbugs.gnu.org
Subject: bug#28833: 26.0.90; Mention how to CC > 2 address in a bug report
Date: Sat, 14 Oct 2017 19:23:32 +0900 [thread overview]
Message-ID: <87376m3u57.fsf@gmail.com> (raw)
Severity: wishlist
Tag: patch
In Bug#28831 I tried CC to 2 people using
two X-Debbugs-CC headers. That doesn't work.
I suggest add a sentence saying how to do this.
--8<-----------------------------cut here---------------start------------->8---
commit b285b6450680f2169eb593969ee8aa9db0b73145
Author: Tino Calancha <tino.calancha@gmail.com>
Date: Sat Oct 14 19:18:37 2017 +0900
Mention how to send CC to > 1 address in a bug report
* admin/notes/bugtracker (* More detailed information):
mention how to CC to more than 1 address.
diff --git a/admin/notes/bugtracker b/admin/notes/bugtracker
index dfca809dc4..0b1625fdb8 100644
--- a/admin/notes/bugtracker
+++ b/admin/notes/bugtracker
@@ -95,13 +95,16 @@ normal bug reporting.)
** When reporting a new bug, to send a Cc to another address
(e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header.
-Instead, use "X-Debbugs-CC:". This ensures the Cc address will get a
+Instead, use "X-Debbugs-CC:". This ensures the Cc address(es) will get a
mail with the bug report number in. If you do not do this, each reply
in the subsequent discussion might end up creating a new bug.
This is annoying. (So annoying that a form of message-id tracking has
been implemented to hopefully stop this happening, but it is still
better to use X-Debbugs-CC.)
+If you want to send copies to more than one address, add them
+comma-separated in only one X-Debbugs-CC line.
+
Like any X-Debbugs- header, this one can also be specified in the
pseudo-header (see below), if your mail client does not let you add
"X-" headers.
--8<-----------------------------cut here---------------end--------------->8---
In GNU Emacs 26.0.90 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.11)
of 2017-10-14 built
Repository revision: 4e59ecc646e88a7a756f1850d92fd2b8780513eb
next reply other threads:[~2017-10-14 10:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 10:23 Tino Calancha [this message]
2017-10-18 3:15 ` bug#28833: 26.0.90; Mention how to CC > 2 address in a bug report Tino Calancha
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=87376m3u57.fsf@gmail.com \
--to=tino.calancha@gmail.com \
--cc=28833@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.