From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Trying to prune the registry because it's full; apply: registry max-size limit reached
Date: Fri, 17 Apr 2015 15:48:16 -0400 [thread overview]
Message-ID: <87mw26r0xr.fsf@lifelogs.com> (raw)
In-Reply-To: <87pp7qn7hw.fsf@ericabrahamsen.net>
On Mon, 30 Mar 2015 17:45:47 +0800 Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
EA> Later on I'll make a new defvar (something like
EA> `gnus-registry-pruning-functions') where third-party packages can
EA> register pruning functions. That way, if a package registers a
EA> "precious" key that cause entries to hang around, it can also register a
EA> function for cleaning up after itself.
Eric, thank you so much for dealing with the pruning stuff and working
on the Gnus registry.
I am not sure if such a facility will be necessary. What packages would
use it? Do we have more than one such package?
Ted
next prev parent reply other threads:[~2015-04-17 19:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 6:12 Tassilo Horn
2015-03-30 6:57 ` Eric Abrahamsen
2015-03-30 7:15 ` Eric Abrahamsen
2015-03-30 9:30 ` Tassilo Horn
2015-03-30 9:45 ` Eric Abrahamsen
2015-03-30 11:02 ` Tassilo Horn
2015-04-17 19:48 ` Ted Zlatanov [this message]
2015-04-18 3:22 ` Eric Abrahamsen
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=87mw26r0xr.fsf@lifelogs.com \
--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).