From: Richard M Stallman <rms@gnu.org>
To: Joe Wells <jbw@macs.hw.ac.uk>, 388@emacsbugs.donarmstrong.com
Cc: bug-gnu-emacs@gnu.org, emacs-devel@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 [thread overview]
Message-ID: <E1K7wS4-0003Hh-F0@fencepost.gnu.org> (raw)
In-Reply-To: <86skvjeqdf.fsf_-_@macs.hw.ac.uk> (message from Joe Wells on Wed, 11 Jun 2008 20:14:04 +0100)
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.
next prev parent reply other threads:[~2008-06-15 17:55 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 ` which bug messages should be sent where? (was: Scrolling occasionally stops in *compilation*) Joe Wells
2008-06-11 21:42 ` which bug messages should be sent where? Jason Rumney
2008-06-15 17:55 ` Richard M Stallman [this message]
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=E1K7wS4-0003Hh-F0@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=388@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jbw@macs.hw.ac.uk \
/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).