From: Xavier Maillard <zedek@gnu-rox.org>
Subject: [POLL]: gmane, gnus.ding or list ?
Date: Sat, 18 Sep 2004 20:27:31 +0200 [thread overview]
Message-ID: <plop87acvna0vg.fsf@gnu-rox.org> (raw)
Hello,
Just a quick (and OT) question on the best way to read the ding
ml.
What is the recommended way of doing this ?
I mean, it seems there are huges differences (at least here) in
the achemining time for a message.
I prefer not to use ML (so I don't overload only one host). I
actually have 3 sources to be sure I can get all messages (not
convenient) but certain messages appear in one group but not the
other one (??).
Is gnus.ding better to use than its gmane equivalent ?
What are the big differences between the two ?
Thank you
--
Xavier Maillard, zedek@gnu-rox.org
next reply other threads:[~2004-09-18 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-18 18:27 Xavier Maillard [this message]
2004-09-19 20:01 ` Reiner Steib
2004-09-19 20:45 ` Jesper Harder
2004-09-20 5:38 ` Xavier Maillard
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=plop87acvna0vg.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).