From: Ian Soboroff <org@acm.isoboroff>
Subject: Re: obstreperousness. gnusers.
Date: Mon, 23 Dec 2002 17:10:18 -0500 [thread overview]
Message-ID: <9cfsmwo75f9.fsf@rogue.ncsl.nist.gov> (raw)
In-Reply-To: <y44k7i3z8la.fsf@nestle.ai.mit.edu>
Don Saklad <dsaklad@nestle.ai.mit.edu> writes:
> A number of people looking for encouragement have written that they
> don't want to use the newsgroup forum gnu.emacs.gnus
Huh? I've been lurking and occasionally posting here for heaven knows
how long, and while trolls aren't tolerated, I don't think I've _ever_
seen anyone with a "How do I ..." question flamed.
(Excepting the long and perhaps honourable history of folks wanting to
have a different From header. But that's actually a nice tendancy to
want to uphold RFC standards.)
I can't count the number of times I've seen Kai walk someone through
something in Gnus. I actually ran into him at a conference this past
summer, and he was kind enough to answer a Gnus question there, too.
Now, there's a fair comment that many of these questions perhaps
shouldn't _have_ to be asked, they should already be set up for you.
So write your how-to or newbie FAQ or whatever and put it on the web.
That's what the web's for. But for petes sake, spend your time there
rather than flaming folks here.
ian
parent reply other threads:[~2002-12-23 22:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <y44k7i3z8la.fsf@nestle.ai.mit.edu>]
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=9cfsmwo75f9.fsf@rogue.ncsl.nist.gov \
--to=org@acm.isoboroff \
/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).