From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: [POLL]: gmane, gnus.ding or list ?
Date: Mon, 20 Sep 2004 07:38:48 +0200 [thread overview]
Message-ID: <plop873c1dbitz.fsf@gnu-rox.org> (raw)
In-Reply-To: <m3mzzmugwt.fsf@defun.localdomain>
On 19 sep 2004, Jesper Harder wrote:
> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
>
> > At least in gnus.gnus-bug there's more spam then in gegg and
> > other Gmane groups when filtering on gmane.spam.detected.
>
> Yeah, gnus-bug is really heavily hit by by spam. Maybe it'd be
> nice to have it on gmane if it could increase the signal/noise
> ratio.
According to your taste, the recommended group is to use gmane.
Why then Lars is maintaining news.gnus.org when he is
doing/working on gmane ?
Just curious.
/me who is about to switch back to gmane...
--
In Gruuik we trust
next prev parent reply other threads:[~2004-09-20 5:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-18 18:27 Xavier Maillard
2004-09-19 20:01 ` Reiner Steib
2004-09-19 20:45 ` Jesper Harder
2004-09-20 5:38 ` Xavier Maillard [this message]
2004-09-20 21:22 ` Jesper Harder
2004-09-20 21:55 ` Xavier Maillard
2004-09-21 1:25 ` Maciej Matysiak
2004-09-22 16:25 ` Xavier Maillard
2004-09-27 5:24 ` Steinar Bang
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=plop873c1dbitz.fsf@gnu-rox.org \
--to=zedek@gnu-rox.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).