unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 7143@debbugs.gnu.org
Subject: bug#7143: Acknowledgement (message.el user References control)
Date: Mon, 04 Oct 2010 15:59:59 -0400	[thread overview]
Message-ID: <lovd5hloe8.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m3ocbdoe7e.fsf@quimbies.gnus.org>

Stefan Monnier wrote:

> Can we have a rule that an email with "Re:" won't create a new bug?

I do not know how to implement that, and I imagine it would be wrong
more often than right. Eg discussing something on emacs-devel, someone
says file that as a bug, someone cc's bug-gnu-emacs on a reply to do
just that.

(I already fixed it so that messages in reply-to existing reports but
without the appropriate subject or to address are appended to those
reports rather than creating new bugs, based on the References and
In-Reply-To headers.)
 
It's not like replying to messages > 2 years old is common.
I plan to just delete this bug from the database in a week or so.





      reply	other threads:[~2010-10-04 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <jwvr6mxjoc9.fsf-monnier+emacs@gnu.org>
     [not found] ` <87y7h3lwbe.fsf@jidanni.org>
     [not found]   ` <v9hcnf567r.fsf@marauder.physik.uni-ulm.de>
     [not found]     ` <jwvmyx6v9a1.fsf-monnier+emacs@gnu.org>
2010-10-01 20:22       ` bug#7143: message.el user References control Lars Magne Ingebrigtsen
     [not found]         ` <handler.7143.B.12859644025155.ack@debbugs.gnu.org>
2010-10-01 20:50           ` bug#7143: Acknowledgement (message.el user References control) Lars Magne Ingebrigtsen
2010-10-01 21:44             ` Glenn Morris
2010-10-03 22:44               ` Stefan Monnier
2010-10-04 19:59                 ` Glenn Morris [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

  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=lovd5hloe8.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=7143@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).