From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: [Eric Knauel] spam.el and spamoracle
Date: Mon, 09 Jun 2003 16:53:07 -0400 [thread overview]
Message-ID: <4nwufv0y8c.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <vw3llwgg99n.fsf@informatik.uni-tuebingen.de> (Eric Knauel's message of "Thu, 05 Jun 2003 11:32:04 +0200")
OK, I've added the spamoracle stuff with some fixes. Please look at
the code and docs, and let me know if I missed anything. Test it :)
By the way (for Gnus Texinfo users), should we use @var in Texinfo?
It's in use here and there, but @code seems much more prevalent. I've
been using @code because I thought @var was not compatible with older
Texinfo versions, but I see @var in a few places now...
Thanks
Ted
next prev parent reply other threads:[~2003-06-09 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 15:57 Lars Magne Ingebrigtsen
2003-05-08 13:44 ` Ted Zlatanov
2003-05-13 17:50 ` Lars Magne Ingebrigtsen
2003-05-13 20:08 ` Eric Knauel
2003-05-13 22:44 ` Lars Magne Ingebrigtsen
2003-05-20 17:41 ` Ted Zlatanov
2003-06-05 9:32 ` Eric Knauel
2003-06-09 20:53 ` Ted Zlatanov [this message]
2003-06-09 23:08 ` Jesper Harder
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=4nwufv0y8c.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).