bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#392: marked as done (duplicate messages on bug-gnu-emacs via emacsbu


From: Emacs bug Tracking System
Subject: bug#392: marked as done (duplicate messages on bug-gnu-emacs via emacsbugs@donarmstrong)
Date: Fri, 22 Jan 2010 20:37:02 +0000

Your message dated Fri, 22 Jan 2010 15:36:26 -0500
with message-id <bjvdetvpv9.fsf@fencepost.gnu.org>
and subject line Re: Bug#897
has caused the Emacs bug report #897,
regarding duplicate messages on bug-gnu-emacs via emacsbugs@donarmstrong
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact bug-gnu-emacs@gnu.org
immediately.)


-- 
897: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=897
Emacs Bug Tracking System
Contact bug-gnu-emacs@gnu.org with problems
--- Begin Message --- Subject: duplicate messages on bug-gnu-emacs via emacsbugs@donarmstrong Date: Thu, 12 Jun 2008 09:05:52 +0800
Many messages appear twice here reading on GMANE.org. E.g., when
somebody does
Cc: bug-gnu-emacs@gnu.org, 378@emacsbugs.donarmstrong.com

Can perhaps these two lists not change the Message-ID, so duplicates
can be detected and discarded, or somehow otherwise suppressed. Or
maybe Stefan should just better edit the headers he sends?




--- End Message ---
--- Begin Message --- Subject: Re: Bug#897 Date: Fri, 22 Jan 2010 15:36:26 -0500 User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
Recent changes ought to gradually make duplicate emails less common.
(See bug#5384). This is still not perfect, so I'll open a new, shorter
bug with the remaining issues.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]