|
From: | GNU bug Tracking System |
Subject: | [Emacs-bug-tracker] bug#8105: closed (make sure explanation comes along with control message) |
Date: | Thu, 24 Feb 2011 02:55:02 +0000 |
Your message dated Wed, 23 Feb 2011 21:54:12 -0500 with message-id <address@hidden> 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 address@hidden) -- 8105: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8105 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---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.
--- End Message ---
--- Begin Message ---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.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |