Subject: bug#8105: closed (Re: make sure explanation comes along with control message)

From: [email-masked] (GNU bug Tracking System)
Date: Thu, 24 Feb 2011 02:55:02 +0000

Your bug report

#8105: make sure explanation comes along with control message

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
8105: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8105
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: make sure explanation comes along with control message
From: Glenn Morris <[email-masked]>
To: [email-masked]
Date: Wed, 23 Feb 2011 21:54:12 -0500
List-Id: <debbugs-submit.debbugs.gnu.org>

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.

Subject: make sure explanation comes along with control message
From: [email-masked]
To: [email-masked]
Cc: Glenn Morris <[email-masked]>
Date: Thu, 24 Feb 2011 10:47:40 +0800
List-Id: <debbugs-submit.debbugs.gnu.org>

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.