From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: ding@gnus.org
Subject: Re: Status of bugs@gnus.org.
Date: Mon, 20 Jun 2005 14:38:39 +0200 [thread overview]
Message-ID: <v9y895w6cw.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87is09o0wg.fsf@xs4all.nl> (Lute Kamstra's message of "Mon, 20 Jun 2005 11:03:43 +0200")
On Mon, Jun 20 2005, Lute Kamstra wrote:
> I'm a GNU Emacs developer and, as you probably know, commits to
> lisp/gnus in Emacs' CVS will go to the stable branch of Gnus' CVS as
> well. So when I want to commit something to lisp/gnus I sometimes
> write a message to bugs@gnus.org to discuss my intended change. In my
> experience, I either get no response or it takes a long time. This
> leaves me wondering if bugs@gnus.org is the right platform for such
> discussions. Should I propose patches to Gnus here instead?
Yes, I'd recommend to use this list (ding@gnus.org).
In contrast to bugs@gnus.org it is carried on Gmane.org, it has a nice
searchable threaded web interface [1] to browse old threads and has
much better spam filtering (when read as a newsgroup from
news.gmane.org). I didn't read bugs@gnus.org for a week and it was
very hard to discover your message (Subject: Major mode conventions)
between all the spam. There were only to ham messages and more than
hundred spam messages.
Two or three years ago, I tried to convince Lars to include
bugs@gnus.org on Gmane, too (this would also solve the spam problem).
But he rejected the idea because he didn't want all the user settings
(created by `M-x gnus-bug RET') to be visible through the web
interface. Since then, the spam/ham ration even got worse and it's
not good when bug reports remain unprocessed because of this.
Bye, Reiner.
[1] http://news.gmane.org/gmane.emacs.gnus.general
http://dir.gmane.org/gmane.emacs.gnus.general
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2005-06-20 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 9:03 Lute Kamstra
2005-06-20 12:38 ` Reiner Steib [this message]
2005-06-20 12:50 ` Romain Francoise
2005-06-21 8:11 ` Lute Kamstra
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=v9y895w6cw.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).