From: Ken Raeburn <raeburn@raeburn.org>
Cc: Gnus Beta Testers <ding@gnus.org>
Subject: Re: nnml compaction
Date: Mon, 19 Sep 2005 13:38:45 -0700 [thread overview]
Message-ID: <ED024564-5BFE-40C1-BE7A-FD10B02DB3B2@raeburn.org> (raw)
In-Reply-To: <muxd5n589tn.fsf@uzeb.lrde.epita.fr>
On Sep 19, 2005, at 06:29, Didier Verna wrote:
> This feature is fully functional for me, but should probably still be
> considered beta. In particular, it correctly preserves marks, but
> nothing is
> written to support the agent or the cache. I don't know these
> beasts and I
> don't even know whether I should be concerned by them. Any
> expertise on the
> matter would be appreciated. Also, there is still a display problem
> with the
> server compaction function: it doesn't update the information in
> the Group
> Buffer.
>
Are you updating xref data too? Both in the message file (or files,
in the case where hard-linking doesn't work) and in the overview
files of other groups?
Ken
next prev parent reply other threads:[~2005-09-19 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 13:29 Didier Verna
2005-09-19 20:38 ` Ken Raeburn [this message]
2005-09-20 7:40 ` Didier Verna
2005-09-20 10:28 ` Katsumi Yamaoka
2005-09-20 12:59 ` Didier Verna
2005-09-25 22:15 ` Miles Bader
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=ED024564-5BFE-40C1-BE7A-FD10B02DB3B2@raeburn.org \
--to=raeburn@raeburn.org \
--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).