From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Banner removal (was: Creating a custom article treatment funtion?)
Date: 06 Nov 1999 23:07:08 +0100 [thread overview]
Message-ID: <m3bt97e0kz.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <wtnn1tf5jco.fsf@licia.dtek.chalmers.se>
Jonas Steverud <d4jonas@dtek.chalmers.se> writes:
> LAAARRRRSSSS! Put this in the FM so someone (like me) can RT it!
> It was not in the 0.91 manual at least.
It's in 0.97, at least...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-11-06 22:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-18 3:29 Creating a custom article treatment funtion? Emerick Rogul
[not found] ` <wtnpuych5o6.fsf@licia.dtek.chalmers.se>
1999-10-18 19:06 ` Emerick Rogul
1999-10-19 9:36 ` Banner removal (was: Creating a custom article treatment funtion?) Toby Speight
1999-10-19 13:48 ` Steinar Bang
1999-10-19 14:41 ` Emerick Rogul
[not found] ` <wtnn1tf5jco.fsf@licia.dtek.chalmers.se>
1999-11-06 22:07 ` Lars Magne Ingebrigtsen [this message]
1999-10-18 22:10 ` Creating a custom article treatment funtion? Kai Großjohann
1999-11-06 22:09 ` Lars Magne Ingebrigtsen
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=m3bt97e0kz.fsf@quimbies.gnus.org \
--to=larsi@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).