GNU bug report logs - #8105
make sure explanation comes along with control message

Previous Next

Package: emacs;

Reported by: jidanni <at> jidanni.org

Date: Thu, 24 Feb 2011 02:48:02 UTC

Severity: wishlist

Tags: notabug, wontfix

Merged with 9071

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Glenn Morris <rgm <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#8105: closed (make sure explanation comes along with control
 message)
Date: Thu, 24 Feb 2011 02:55:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Wed, 23 Feb 2011 21:54:12 -0500
with message-id <19813.51284.965324.833732 <at> fencepost.gnu.org>
and subject line Re: make sure explanation comes along with control message
has caused the GNU bug report #8105,
regarding make sure explanation comes along with control message
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
8105: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8105
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: jidanni <at> jidanni.org
To: bug-gnu-emacs <at> gnu.org
Cc: Glenn Morris <rgm <at> gnu.org>
Subject: make sure explanation comes along with control message
Date: Thu, 24 Feb 2011 10:47:40 +0800
Can you make it easier for developers to send some content along with their
#1463 acknowledged by developer (control message for bug 1462)
#1462 acknowledged by developer (control message for bug 1462)
#1465 acknowledged by developer (control message for bug 1462)

We just get lots of
'You should be hearing from them with a substantive response shortly,
in case you haven't already. If not, please contact them directly.'

Which didn't work either.


[Message part 3 (message/rfc822, inline)]
From: Glenn Morris <rgm <at> gnu.org>
To: 8105-done <at> debbugs.gnu.org
Subject: Re: make sure explanation comes along with control message
Date: Wed, 23 Feb 2011 21:54:12 -0500
You open large quantities of extremely low quality reports.
I am not obliged to provide you with an explanation as to why 
each and every one is closed. It will be clear to anyone who reads them.


This bug report was last modified 13 years and 319 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.