bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#28833: 26.0.90; Mention how to CC > 2 address in a bug report


From: Tino Calancha
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

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





reply via email to

[Prev in Thread] Current Thread [Next in Thread]