From: Karl Kleinpaste <invalid@kleinpaste.org>
To: info-gnus-english@gnu.org
Subject: Re: Switching backends
Date: Wed, 02 May 2007 09:09:29 -0400 [thread overview]
Message-ID: <yu0abwngynq.fsf@mesquite.kleinpaste.org> (raw)
In-Reply-To: <mailman.87.1178110556.32220.info-gnus-english@gnu.org>
Sebastian Tennant <sebyte@smolny.plus.com> writes:
> Switching backends isn't a problem, but how to perform the migration
> of already 'processed' mail?
Create new nnml equivalents of old nnfolder groups.
Enter an nnfolder group.
If you care about the order in which the articles will be moved, then
re-sort it e.g. by date with `C-c C-s C-d'.
`M P a' to process-mark all articles.
`B m' to move the articles, selecting the equivalent nnml group.
Once you're sure that everything has moved as expected, arrange to
delete old nnfolder groups in *Group* with `G DEL'.
next parent reply other threads:[~2007-05-02 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.87.1178110556.32220.info-gnus-english@gnu.org>
2007-05-02 13:09 ` Karl Kleinpaste [this message]
2007-05-02 12:05 Sebastian Tennant
2007-05-02 14:28 ` Kai Grossjohann
2007-05-02 18:43 ` Reiner Steib
2007-05-02 21:38 ` Sebastian Tennant
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=yu0abwngynq.fsf@mesquite.kleinpaste.org \
--to=invalid@kleinpaste.org \
--cc=MyGivenName+usenet@kleinpaste.org \
--cc=info-gnus-english@gnu.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).