GNU bug report logs -
#28833
26.0.90; Mention how to CC > 2 address in a bug report
Previous Next
Reported by: Tino Calancha <tino.calancha <at> gmail.com>
Date: Sat, 14 Oct 2017 10:24:02 UTC
Severity: wishlist
Found in version 26.0.90
Done: Tino Calancha <tino.calancha <at> gmail.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 28833 in the body.
You can then email your comments to 28833 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#28833
; Package
emacs
.
(Sat, 14 Oct 2017 10:24:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Tino Calancha <tino.calancha <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sat, 14 Oct 2017 10:24:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
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 <at> 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 <at> 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 sent
to
Tino Calancha <tino.calancha <at> gmail.com>
:
You have taken responsibility.
(Wed, 18 Oct 2017 03:17:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Tino Calancha <tino.calancha <at> gmail.com>
:
bug acknowledged by developer.
(Wed, 18 Oct 2017 03:17:04 GMT)
Full text and
rfc822 format available.
Message #10 received at 28833-done <at> debbugs.gnu.org (full text, mbox):
Tino Calancha <tino.calancha <at> gmail.com> writes:
> 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.
> +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.
Pushed into emacs-26 branch as commit
"Mention how to send CC to > 1 address in a bug report"
(445e92658f16255b30b359e296d301fa6b929872)
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 15 Nov 2017 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 7 years and 221 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.