From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: `gnus-agent-expire' - specifics?
Date: 23 Mar 1998 14:25:33 +0100 [thread overview]
Message-ID: <m3btuxtu7m.fsf@sparky.gnus.org> (raw)
In-Reply-To: Mike McEwan's message of "22 Mar 1998 16:09:57 +0000"
Mike McEwan <mike@lotusland.demon.co.uk> writes:
> An alternative would be to have a separate `history' file for
> downloaded headers, but then there's probably too many files already
> eh.
Since the .overview file shows the relative age of articles, I think
the expiry function should just delete all header lines that have
lower article numbers than the youngest of the expirable articles.
> Just an idea, I'm in no way proffering this as the way to go, it's
> just that I've wasted some time on it :-). What's the deal with those
> .agentview files? I been pruning my .overviews, but these suckers seem
> to keep on growing (I think...).
Oops. I forgot about those as well.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-03-23 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-18 21:42 Mike McEwan
1998-03-19 13:28 ` Lars Magne Ingebrigtsen
1998-03-22 16:09 ` Mike McEwan
1998-03-23 13:25 ` Lars Magne Ingebrigtsen [this message]
1998-03-23 23:47 ` Mike McEwan
1998-03-26 14:50 ` 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=m3btuxtu7m.fsf@sparky.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).