From: Joe Wells <jbw@macs.hw.ac.uk>
To: rms@gnu.org
Cc: bug-gnu-emacs@gnu.org, bug-submit-list@donarmstrong.com,
drew.adams@oracle.com, emacs-devel@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 [thread overview]
Message-ID: <86skvjeqdf.fsf_-_@macs.hw.ac.uk> (raw)
In-Reply-To: <E1K6UOO-00058f-43@fencepost.gnu.org> (Richard M. Stallman's message of "Wed\, 11 Jun 2008 13\:45\:52 -0400")
[ 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@gnu.org> writes:
> Any e-mail sent to XYZ@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@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.
next prev parent reply other threads:[~2008-06-11 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 19:02 bug#21: Scrolling occasionally stops in *compilation* Stefan Monnier
2008-06-10 19:47 ` Drew Adams
[not found] ` <mailman.13010.1213128432.18990.bug-gnu-emacs@gnu.org>
2008-06-11 10:23 ` Joe Wells
2008-06-11 13:28 ` Drew Adams
2008-06-11 17:45 ` Richard M Stallman
2008-06-11 18:50 ` Don Armstrong
2008-06-11 19:14 ` Joe Wells [this message]
2008-06-11 21:42 ` which bug messages should be sent where? Jason Rumney
2008-06-15 17:55 ` bug#388: which bug messages should be sent where? (was: Scrolling occasionally stops in *compilation*) Richard M Stallman
2010-03-17 16:12 ` bug#21: Scrolling occasionally stops in *compilation* Glenn Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86skvjeqdf.fsf_-_@macs.hw.ac.uk \
--to=jbw@macs.hw.ac.uk \
--cc=bug-gnu-emacs@gnu.org \
--cc=bug-submit-list@donarmstrong.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).