unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#8105: make sure explanation comes along with control message
@ 2011-02-24  2:47 ` jidanni
  2011-02-24  2:54   ` Glenn Morris
                     ` (5 more replies)
  0 siblings, 6 replies; 9+ messages in thread
From: jidanni @ 2011-02-24  2:47 UTC (permalink / raw)
  To: 8105

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.





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#8105: make sure explanation comes along with control message
  2011-02-24  2:47 ` bug#8105: make sure explanation comes along with control message jidanni
@ 2011-02-24  2:54   ` Glenn Morris
  2011-02-24  3:22   ` bug#8105: closed (Re: make sure explanation comes along with control message) jidanni
                     ` (4 subsequent siblings)
  5 siblings, 0 replies; 9+ messages in thread
From: Glenn Morris @ 2011-02-24  2:54 UTC (permalink / raw)
  To: 8105-done


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.





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#8105: closed (Re: make sure explanation comes along with control message)
  2011-02-24  2:47 ` bug#8105: make sure explanation comes along with control message jidanni
  2011-02-24  2:54   ` Glenn Morris
@ 2011-02-24  3:22   ` jidanni
  2011-02-24  6:35   ` bug#8105: make sure submitter automatically gets reason jidanni
                     ` (3 subsequent siblings)
  5 siblings, 0 replies; 9+ messages in thread
From: jidanni @ 2011-02-24  3:22 UTC (permalink / raw)
  To: 8105

All I know is with the bugs closed by rgm@gnu.org, one must do several
actions to read the reason, whereas with the bugs closed on Debian, the
reason comes along right there in the same message.





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#8105: make sure submitter automatically gets reason
  2011-02-24  2:47 ` bug#8105: make sure explanation comes along with control message jidanni
  2011-02-24  2:54   ` Glenn Morris
  2011-02-24  3:22   ` bug#8105: closed (Re: make sure explanation comes along with control message) jidanni
@ 2011-02-24  6:35   ` jidanni
  2011-02-24 18:44     ` Eli Zaretskii
  2011-02-24 22:55   ` jidanni
                     ` (2 subsequent siblings)
  5 siblings, 1 reply; 9+ messages in thread
From: jidanni @ 2011-02-24  6:35 UTC (permalink / raw)
  To: 8105

All I know is on all the other bug trackers I've used, the submitter
gets all the same information the bug closer left in the records upon
closing the bug. I mean (unless it was closed by spam) there is a
message the closer left as to why he closed the bug, and the debbugs
software should be adjusted to make sure the submitter gets it. Else the
submitter is only left with a bug email address (not even a URL), to look
to for further information.





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#8105: make sure submitter automatically gets reason
  2011-02-24  6:35   ` bug#8105: make sure submitter automatically gets reason jidanni
@ 2011-02-24 18:44     ` Eli Zaretskii
  0 siblings, 0 replies; 9+ messages in thread
From: Eli Zaretskii @ 2011-02-24 18:44 UTC (permalink / raw)
  To: jidanni; +Cc: 8105

> From: jidanni@jidanni.org
> Date: Thu, 24 Feb 2011 14:35:09 +0800
> Cc: 
> 
> All I know is on all the other bug trackers I've used, the submitter
> gets all the same information the bug closer left in the records upon
> closing the bug. I mean (unless it was closed by spam) there is a
> message the closer left as to why he closed the bug, and the debbugs
> software should be adjusted to make sure the submitter gets it.

That's how it works already, AFAIK.  At least I always get a message
when someone closes a bug I filed.  If you have evidence that it
doesn't work for you, please show it, and we will try to make sure
this doesn't happen in the future.





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#8105: make sure submitter automatically gets reason
  2011-02-24  2:47 ` bug#8105: make sure explanation comes along with control message jidanni
                     ` (2 preceding siblings ...)
  2011-02-24  6:35   ` bug#8105: make sure submitter automatically gets reason jidanni
@ 2011-02-24 22:55   ` jidanni
  2011-02-24 23:03     ` Don Armstrong
  2011-02-24 23:12   ` jidanni
  2011-02-25  8:25   ` bug#8105: add URL to the 'bug closed' message jidanni
  5 siblings, 1 reply; 9+ messages in thread
From: jidanni @ 2011-02-24 22:55 UTC (permalink / raw)
  To: don, eliz; +Cc: 8105

>>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
>> From: jidanni@jidanni.org
>> All I know is on all the other bug trackers I've used, the submitter
>> gets all the same information the bug closer left in the records upon
>> closing the bug. I mean (unless it was closed by spam) there is a
>> message the closer left as to why he closed the bug, and the debbugs
>> software should be adjusted to make sure the submitter gets it.

EZ> That's how it works already, AFAIK.  At least I always get a message
EZ> when someone closes a bug I filed.  If you have evidence that it
EZ> doesn't work for you, please show it, and we will try to make sure
EZ> this doesn't happen in the future.

Don Armstrong: along with the "you should be hearing from them soon"
message, could you at least please put the URL for the bug, with best #
anchor too, into the text of those messages, on both the Emacs and
Debian BTS. Thanks!





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#8105: make sure submitter automatically gets reason
  2011-02-24 22:55   ` jidanni
@ 2011-02-24 23:03     ` Don Armstrong
  0 siblings, 0 replies; 9+ messages in thread
From: Don Armstrong @ 2011-02-24 23:03 UTC (permalink / raw)
  To: jidanni; +Cc: 8105

On Fri, 25 Feb 2011, jidanni@jidanni.org wrote:
> Don Armstrong: along with the "you should be hearing from them soon"
> message, could you at least please put the URL for the bug, with
> best # anchor too, into the text of those messages, on both the
> Emacs and Debian BTS.

I don't have anything to do with the GNU debbugs install anymore.


Don Armstrong

-- 
Democracy is more dangerous than fire. Fire can't vote itself immune
to water.
 -- Michael Z. Williamson

http://www.donarmstrong.com              http://rzlab.ucr.edu





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#8105: make sure submitter automatically gets reason
  2011-02-24  2:47 ` bug#8105: make sure explanation comes along with control message jidanni
                     ` (3 preceding siblings ...)
  2011-02-24 22:55   ` jidanni
@ 2011-02-24 23:12   ` jidanni
  2011-02-25  8:25   ` bug#8105: add URL to the 'bug closed' message jidanni
  5 siblings, 0 replies; 9+ messages in thread
From: jidanni @ 2011-02-24 23:12 UTC (permalink / raw)
  To: eliz, don; +Cc: 8105

>>>>> "DA" == Don Armstrong <don@donarmstrong.com> writes:
DA> On Fri, 25 Feb 2011, jidanni@jidanni.org wrote:
>> Don Armstrong: along with the "you should be hearing from them soon"
>> message, could you at least please put the URL for the bug, with
>> best # anchor too, into the text of those messages, on both the
>> Emacs and Debian BTS.

DA> I don't have anything to do with the GNU debbugs install anymore.

How about on Debian? Can you make it add the URLs there?





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#8105: add URL to the 'bug closed' message
  2011-02-24  2:47 ` bug#8105: make sure explanation comes along with control message jidanni
                     ` (4 preceding siblings ...)
  2011-02-24 23:12   ` jidanni
@ 2011-02-25  8:25   ` jidanni
  5 siblings, 0 replies; 9+ messages in thread
From: jidanni @ 2011-02-25  8:25 UTC (permalink / raw)
  To: submit; +Cc: 8105

X-debbugs-Cc: don@donarmstrong.com
Package: bugs.debian.org
Severity: wishlist

Please add the URL to closed message just like in
http://debbugs.gnu.org/8105 . Thanks.


>>>>> "DA" == Don Armstrong <don@donarmstrong.com> writes:
DA> I don't have anything to do with the GNU debbugs install anymore.
Somebody apparently reading this added the URLs on debbugs starting just
today!

DA> File a bug if there isn't already one and it doesn't already do it.
DA> ISTR changing the code to add the URIs a while ago.
OK here's the bug.





^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2011-02-25  8:25 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <handler.8105.D8105.129851606020277.notifdone@debbugs.gnu.org>
2011-02-24  2:47 ` bug#8105: make sure explanation comes along with control message jidanni
2011-02-24  2:54   ` Glenn Morris
2011-02-24  3:22   ` bug#8105: closed (Re: make sure explanation comes along with control message) jidanni
2011-02-24  6:35   ` bug#8105: make sure submitter automatically gets reason jidanni
2011-02-24 18:44     ` Eli Zaretskii
2011-02-24 22:55   ` jidanni
2011-02-24 23:03     ` Don Armstrong
2011-02-24 23:12   ` jidanni
2011-02-25  8:25   ` bug#8105: add URL to the 'bug closed' message jidanni

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).