Gnus development mailing list
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
To: Miles Bader <miles.bader@necel.com>
Cc: ding@gnus.org
Subject: Re: Usage of gnus mailing list mode
Date: Sun, 31 Aug 2008 12:32:23 +0900	[thread overview]
Message-ID: <87fxolj1vc.fsf@catnip.gol.com> (raw)
In-Reply-To: <87r688s3af.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Fri, 29 Aug 2008 09:12:24 +0200")

Tassilo Horn <tassilo@member.fsf.org> writes:
>> It is indeed a (very long-standing) convention, with a pretty good
>> justification -- when you're not _sure_ the other person reads the
>> list, it's better to be safe than sorry.  And you can't be sure, in
>> general.
>
> Well, ok.  Sometimes that may be correct.  But most mailing lists allow
> posting only by subscribers, so there's no reason to handle the issue
> that the original poster doesn't read the list.

Unless you can show that is true of _all_ mailing lists, or at least
something like 99% (and though subscriber-only lists are pretty common
these days, I suspect you can't -- indeed many GNU lists allow posting
by non-subscribers), then there certainly is a reason to use the safer
default.

If Gnus happens to have more information about a particular mailing
list, of course it could try to be more clever in that case.

-Miles

-- 
Erudition, n. Dust shaken out of a book into an empty skull.



  reply	other threads:[~2008-08-31  3:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 14:55 Tassilo Horn
2008-08-22  9:28 ` David Engster
2008-08-22 10:45   ` Tassilo Horn
2008-08-22 11:32     ` Tassilo Horn
2008-08-22 11:58       ` David Engster
2008-08-22 13:40         ` Tassilo Horn
2008-08-22 13:59           ` David Engster
2008-08-29  4:52 ` Miles Bader
2008-08-29  7:12   ` Tassilo Horn
2008-08-31  3:32     ` Miles Bader [this message]
2008-09-01  7:06       ` Tassilo Horn

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=87fxolj1vc.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=ding@gnus.org \
    --cc=miles.bader@necel.com \
    /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).