GNU bug report logs - #388
which bug messages should be sent where? (was: Scrolling occasionally stops in *compilation*)

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 388 in the body.
You can then email your comments to 388 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Joe Wells <jbw <at> macs.hw.ac.uk>
To: rms <at> gnu.org
Cc: drew.adams <at> oracle.com, bug-submit-list <at> donarmstrong.com,
        bug-gnu-emacs <at> gnu.org, emacs-devel <at> gnu.org
Subject: which bug messages should be sent where? (was: Scrolling occasionally stops in *compilation*)
Date: Wed, 11 Jun 2008 20:14:04 +0100

[ I am removing “bug#21” from the subject because it seems this
  triggers the bug tracker to add the message to the log for this bug
  in the bug tracker.  Can someone please post a description of the
  complete interface? ]

Richard M Stallman <rms <at> gnu.org> writes:

>     Any e-mail sent to XYZ <at> emacsbugs.donarmstrong.com (where XYZ is the
>     bug number) will be CC-ed to bug-gnu-emacs automatically.  This is
>     what Stefan did.
>
> That is a pain in the neck for everyone on bug-gnu-emacs.
> It should be cc'd to emacs-bug-tracker instead.
>
>     It is good that e-mail sent to XYZ <at> emacsbugs.donarmstrong.com is CC-ed
>     to bug-gnu-emacs automatically.  Simply turning this off would be bad.
>
> I don't see anything bad about it.
> Would you like to try to substantiate that statement?

The important question is:

  What is the purpose of the bug-gnu-emacs mailing list (and the
  gnu.emacs.bug newsgroup which is connected to the mailing list)?

It is very good that there is now a bug tracker for Emacs.

However, the existence of the bug tracker means the purpose of the
bug-gnu-emacs mailing list needs to be reassessed.

I believe the purpose of the bug-gnu-emacs mailing list should now be
this:

  The bug-gnu-emacs mailing list is (1) where people can send bug
  reports and (2) where people who want to help can watch for bug
  reports and the discussion of bug reports.

>     There is no simple solution, although there may be a complicated
>     one.
>
> I've stated a simple solution above.

You could also solve the “problem” by unsubscribing from the mailing
list.

Your “solution” would make it too difficult for people like me to
watch the discussion and contribute where we have useful knowledge to
share.  Your “solution” could make things easier for some people, but
it would also make it harder for other people to help in solving bugs.

I suggest that a long-term solution should be thought about more
carefully.

I hope this message is helpful.

-- 
Joe


-- 
Heriot-Watt University is a Scottish charity
registered under charity number SC000278.

Message #22 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Richard M Stallman <rms <at> gnu.org>
To: Joe Wells <jbw <at> macs.hw.ac.uk>, 388 <at> debbugs.gnu.org
Cc: bug-gnu-emacs <at> gnu.org, emacs-devel <at> gnu.org
Subject: Re: bug#388: which bug messages should be sent where? (was: Scrolling
	occasionally stops in *compilation*)
Date: Sun, 15 Jun 2008 13:55:40 -0400

    Your ?solution? would make it too difficult for people like me to
    watch the discussion and contribute where we have useful knowledge to
    share.

With all due respect, I think your conclusion is mistaken.
My solution would not inconvenience you at all.

My solution would involve sending these messages to emacs-bug-tracker
instead of to bug-gnu-emacs.  If you want to see these messages,
you could subscribe to emacs-bug-tracker, and you would get the
same messages you are getting now.

This change would give each subscriber on bug-gnu-emacs the option to
either receive the bug-tracker mail or not.  I don't think that can
make anything difficult for anyone, and I do not understand why some
people resist making the change.

Previous Next

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