unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16691@debbugs.gnu.org, lekktu@gmail.com
Subject: bug#16691: 24.3.50; emacs_backtrace.txt
Date: Sat, 08 Feb 2014 15:40:25 -0500	[thread overview]
Message-ID: <7fiospwd6u.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83zjm1uz1g.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 08 Feb 2014 22:31:23 +0200")


If you bcc'd control@debbugs rather than cc'ing, you would not have the
problem where people, including yourself, include it on all future replies.

You've previously said you won't do that, but I ask you to reconsider:

http://lists.gnu.org/archive/html/emacs-devel/2013-08/msg00804.html

>> If control@debbugs goes in BCC, people will become confused about
>> those weird commands at the beginning of the message.

That supposes that people 1) read the address list (my experience is
that they do not, you're proving it in this thread); and 2) use it
figure out what "weird commands" might mean (I doubt it).

By not using bcc, you require everyone who might reply to you to check
and possibly edit the reply list, or to start every single message with
"stop". (Or to use something like message-dont-reply-to-names, which is
a good idea anyway.)

If you really think people are confused by these commands, you should
send them in a totally separate message. Or preface them with a #
comment to explain them.





  reply	other threads:[~2014-02-08 20:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 17:30 bug#16691: 24.3.50; emacs_backtrace.txt Drew Adams
2014-02-08 19:22 ` Juanma Barranquero
2014-02-08 19:34   ` Eli Zaretskii
2014-02-08 20:06     ` martin rudalics
2014-02-08 20:31       ` Eli Zaretskii
2014-02-08 20:40         ` Glenn Morris [this message]
2014-02-08 20:55           ` Eli Zaretskii
2014-02-08 23:25             ` Glenn Morris
2014-02-09 11:04         ` martin rudalics
2014-02-09 16:30           ` Eli Zaretskii
2014-02-09 18:58             ` martin rudalics
2014-02-09 20:20               ` Eli Zaretskii
2014-02-10  8:14                 ` martin rudalics
2014-02-10 17:42                   ` Eli Zaretskii
2014-02-10 18:35                     ` martin rudalics
2014-02-10 18:44                       ` Eli Zaretskii
2015-12-26 13:26                         ` Lars Ingebrigtsen
2015-12-26 13:38                           ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7fiospwd6u.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=16691@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=lekktu@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).