From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: nnima-split-with-parent
Date: Mon, 09 Dec 2002 10:54:23 -0500 [thread overview]
Message-ID: <4n3cp789xs.fsf@brainy.bwh.harvard.edu> (raw)
In-Reply-To: <84of7xpof5.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Sat, 07 Dec 2002 21:25:02 +0100")
On Sat, 07 Dec 2002, kai.grossjohann@uni-duisburg.de wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> On Sat, 07 Dec 2002, kai.grossjohann@uni-duisburg.de wrote:
>>> But this doesn't deal with the unqualified group names that are
>>> currently in the file.
>>
>> We convert them to the nnmail-cache-primary-backend:groupname fully
>> qualified format. Wouldn't that make sense?
>
> Usually, an unqualified group name is assumed to come from the
> primary backend (ie, gnus-select-method). So it's not sufficient to
> _just_ call the functions I gave.
Here are the upgrade steps when running nnimap-split-with-parent, when
it needs to load the history-cache:
1) does the history-cache (nnmail cache version 2) file exist? if
yes, go to (3)
2) upgrade ~/.nnmail-cache to a new history-cache file, or create a
new history-cache file if ~/.nnmail-cache does not exist
a) creating a new file: just touch the file
b) upgrading: all lines get prefixed with the return value of
nnmail-cache-primary-backend, then a \t character
3) load the history-cache file with the
"backend\tmessage-id\tgroupname" format
Does that makes sense? From (3) on, all work is done with the new
history-cache file. The user could even go back to using the old
nnmail-split-with-parent function in their nnmail split, since
~/.nnmail-cache would be the same as before.
Ted
next prev parent reply other threads:[~2002-12-09 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 20:24 nnima-split-with-parent Ted Zlatanov
2002-12-07 14:59 ` nnima-split-with-parent Kai Großjohann
2002-12-07 18:20 ` nnima-split-with-parent Ted Zlatanov
2002-12-07 20:22 ` nnima-split-with-parent Kai Großjohann
[not found] ` <m2k7imroo1.fsf@tnuctip.rychter.com>
2002-12-07 13:54 ` nnimap-split-with-parent Ted Zlatanov
2002-12-07 15:01 ` nnima-split-with-parent Kai Großjohann
2002-12-07 15:14 ` nnima-split-with-parent Ted Zlatanov
2002-12-07 15:28 ` nnima-split-with-parent Kai Großjohann
2002-12-07 18:20 ` nnima-split-with-parent Ted Zlatanov
2002-12-07 20:25 ` nnima-split-with-parent Kai Großjohann
2002-12-09 15:54 ` Ted Zlatanov [this message]
2002-12-09 16:21 ` nnima-split-with-parent Kai Großjohann
[not found] ` <m27kelycce.fsf@tnuctip.rychter.com>
2002-12-07 20:23 ` nnima-split-with-parent Kai Großjohann
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=4n3cp789xs.fsf@brainy.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).