From: Erik Colson <eco@ecocode.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: moving a group from one Imap backend to another
Date: Fri, 13 Feb 2015 09:25:08 +0100 [thread overview]
Message-ID: <m2386arzff.fsf@ecocode.net> (raw)
In-Reply-To: <87egpufgd8.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Fri, 13 Feb 2015 17:57:39 +1100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I'd just enter each group in question, process-mark all the articles and
> then move/copy the articles to the other server.
Thanks Lars
That is what I was fearing... I have literally hundreds of boxes to
move. That would give me certainly a whole day of work, which would be
acceptable, except the handling looks error prone since I would switch
from actual work to Emacs and back on and on. That would most certainly
provoke a collision somewhere between my neurones ;)
--
erik colson
next prev parent reply other threads:[~2015-02-13 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 14:44 Erik Colson
2015-02-13 6:57 ` Lars Ingebrigtsen
2015-02-13 8:25 ` Erik Colson [this message]
2015-02-13 16:29 ` Jason L Tibbitts III
2015-02-24 9:38 ` Alexander Baier
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=m2386arzff.fsf@ecocode.net \
--to=eco@ecocode.net \
--cc=ding@gnus.org \
--cc=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).