all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: Bug tracker automated control server message
Date: Sat, 31 Aug 2013 18:06:28 +0200	[thread overview]
Message-ID: <87fvtp3kvv.fsf@engster.org> (raw)
In-Reply-To: <83bo4edlea.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 31 Aug 2013 16:45:17 +0300")

Eli Zaretskii writes:
>> From: David Engster <deng@randomsample.de>
>> Date: Sat, 31 Aug 2013 15:04:43 +0200
>> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>> 
>> This is why the control@debbugs address should usually go in the BCC, so
>> that people who do a wide reply do not mail the control server by
>> accident.
>
> If control@debbugs goes in BCC, people will become confused about
> those weird commands at the beginning of the message.

I think those commands are pretty clear; before I learned about
control@debbugs, I used to think that the bugtracker simply always
processes them. IMO the messages you get from an accidental mail to the
control server are much weirder; also, as a guideline, using BCC is
recommended in admin/notes/bugtracker.

-David



  reply	other threads:[~2013-08-31 16:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30  4:52 bug#15213: 24.3.50; emacs_backtrace.txt Drew Adams
2013-08-31  1:36 ` Juanma Barranquero
2013-08-31  7:02   ` Eli Zaretskii
2013-08-31  8:16     ` martin rudalics
     [not found]       ` <handler.s.C.137793698428616.transcript@debbugs.gnu.org>
2013-08-31  8:38         ` Bug tracker automated control server message martin rudalics
2013-08-31 11:39           ` Eli Zaretskii
2013-08-31 12:56             ` martin rudalics
2013-08-31 13:04               ` David Engster
2013-08-31 13:07                 ` martin rudalics
2013-08-31 13:45                 ` Eli Zaretskii
2013-08-31 16:06                   ` David Engster [this message]
2013-08-31  9:31       ` bug#15213: 24.3.50; emacs_backtrace.txt martin rudalics
2013-08-31 16:52       ` Drew Adams
2013-08-31 17:35         ` martin rudalics

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=87fvtp3kvv.fsf@engster.org \
    --to=deng@randomsample.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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.