From: Don Armstrong <don@donarmstrong.com>
To: emacs-devel@gnu.org
Cc: submit@emacsbugs.donarmstrong.com
Subject: bug#430: Add MFT to bug reports
Date: Mon, 16 Jun 2008 12:08:49 -0700 [thread overview]
Message-ID: <20080616190849.GO20708__6443.42468954182$1213644509$gmane$org@rzlab.ucr.edu> (raw)
In-Reply-To: <nmbq21xmzv.fsf@fencepost.gnu.org>
Package: emacsbugs.donarmstrong.com
Severity: wishlist
On Mon, 16 Jun 2008, Glenn Morris wrote:
> Please consider adding a Mail-Followup-To header in reports that come
> from the bug tracker, as well as/instead of a Reply-To header.
>
> In emacs mailing lists, the right thing to do has always been to hit
> followup rather than reply. In bug-gnu-emacs, this is no longer right,
> since one ends up with mail going to the submitter, the numbered bug
> address, and the bug list. The last one is superfluous and results in
> duplicate messages (perhaps these are being purged now, but even so).
>
> I'm not going to be able to train my fingers to press a different key
> according to which Emacs mailing list I'm in.
Hrm. I can make this change; the adding of bug-gnus-emacs@ to MFT is
probably a mailman specific setting that can be turned off too, and
then it will work properly.
Don Armstrong
--
NASCAR is a Yankee conspiracy to keep you all placated so the South
won't rise again.
-- http://www.questionablecontent.net/view.php?comic=327
http://www.donarmstrong.com http://rzlab.ucr.edu
prev parent reply other threads:[~2008-06-16 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 18:17 Mail-Followup-To in bug reports Glenn Morris
2008-06-16 19:08 ` Add MFT to " Don Armstrong
2009-12-17 18:14 ` bug#430: marked as done (Add MFT to bug reports) Emacs bug Tracking System
2008-06-16 19:08 ` Don Armstrong [this message]
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='20080616190849.GO20708__6443.42468954182$1213644509$gmane$org@rzlab.ucr.edu' \
--to=don@donarmstrong.com \
--cc=430@emacsbugs.donarmstrong.com \
--cc=emacs-devel@gnu.org \
--cc=submit@emacsbugs.donarmstrong.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 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.