From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Improving the spam.el documentation.
Date: Fri, 28 May 2004 17:00:41 +0200 [thread overview]
Message-ID: <m3k6ywha06.fsf@defun.localdomain> (raw)
In-Reply-To: <87smdk8yxs.fsf@enki.rimspace.net> (Daniel Pittman's message of "Fri, 28 May 2004 23:26:55 +1000")
Daniel Pittman <daniel@rimspace.net> writes:
> So, in the hope that others don't have to suffer through the same
> stuff that I did I have embarked on updating the spam.el
> documentation in the Gnus manual.
One small thing that might be nice would be to move the spam section
one level up.
Now it's buried somewhere in "Various", and since it quite long it
might as well have its own chapter instead.
--
Jesper Harder <http://purl.org/harder/>
next prev parent reply other threads:[~2004-05-28 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 13:26 Daniel Pittman
2004-05-28 15:00 ` Jesper Harder [this message]
2004-05-28 16:27 ` Ted Zlatanov
2004-05-31 13:34 ` Daniel Pittman
2004-06-07 16:56 ` Ted Zlatanov
2004-06-08 1:29 ` Daniel Pittman
2004-06-08 14:31 ` Ted Zlatanov
2004-06-07 17:06 ` Ted Zlatanov
2004-06-08 1:38 ` Daniel Pittman
2004-06-08 2:25 ` Jesper Harder
2004-06-08 3:28 ` Daniel Pittman
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=m3k6ywha06.fsf@defun.localdomain \
--to=harder@ifa.au.dk \
/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).