unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Let's shut down bug-gnu-emacs@gnu.org
Date: Sun, 11 Dec 2005 17:57:03 -0500	[thread overview]
Message-ID: <E1Ela7r-0007id-47@fencepost.gnu.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1051211091856.238A-100000@acm.acm> (message from Alan Mackenzie on Sun, 11 Dec 2005 10:16:25 +0000 (GMT))

    gnu.emacs.bug is supposedly a moderated newsgroup.

Where does it say that?  This group is not moderated, and never was.

    In years past, I actually used gnu.emacs.bug a fair amount to report bugs
    and submit feature requests.  If I were just getting into Emacs now, I
    doubt I'd bother, given the state of this newsgroup.

I can see why you might hesitate to _read_ a list with a lot of spam,
but why, rationally, would the amount of spam affect your decision to
post to the list?  I don't see how it makes any difference.

The list still does its job.  I continue to receive this list, and
when a useful but report or suggestion comes along, I DTRT with it.
There is no reason for people to stop posting to it.

Reducing the spam would be useful.  One thing we could do to reduce
the spam is set things up to reject messages which fail to contain
"emacs" in the subject or body.  If these rejections send back an
auto-reply telling real users what to do, it should not be an
inconvenience.

    In September, I sent an email to postmaster@gnu.org

I don't think anyone reads mail to postmaster any more.
I was told, several years ago, that this was a general practice
on the net.

     offering to do manual
    moderation of help-gnu-emacs.

I did not know about your request.  I might want to take you up on it,
but first let's consider that automatic method.

  reply	other threads:[~2005-12-11 22:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-11 10:16 Let's shut down bug-gnu-emacs@gnu.org Alan Mackenzie
2005-12-11 22:57 ` Richard M. Stallman [this message]
2005-12-11 23:49   ` Andreas Schwab
2005-12-12  5:59   ` Eli Zaretskii
2005-12-12  8:55     ` Ralf Angeli
2005-12-12 20:50       ` Eli Zaretskii
2005-12-12 21:33         ` Ralf Angeli
2005-12-13  3:14     ` Richard M. Stallman
2005-12-12  9:10   ` Alan Mackenzie
2005-12-12 18:49     ` Ken Raeburn
2005-12-12 22:42       ` Reiner Steib
2005-12-12 22:18     ` Xavier Maillard
2005-12-13  6:57     ` Ken Raeburn
2005-12-13 18:48       ` Alan Mackenzie
2005-12-12 14:49   ` Sam Steingold
2005-12-12 15:41   ` Stefan Monnier
2005-12-12 22:18     ` Xavier Maillard
2005-12-12 22:52     ` Reiner Steib
2005-12-13  6:07       ` Bill Wohler

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=E1Ela7r-0007id-47@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@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).