Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Erik Colson <eco@ecocode.net>
Cc: ding@gnus.org
Subject: Re: moving a group from one Imap backend to another
Date: Fri, 13 Feb 2015 17:57:39 +1100	[thread overview]
Message-ID: <87egpufgd8.fsf@building.gnus.org> (raw)
In-Reply-To: <m2lhk5hlmf.fsf@ecocode.net> (Erik Colson's message of "Tue, 10 Feb 2015 15:44:24 +0100")

Erik Colson <eco@ecocode.net> writes:

> How can I move several groups with as minimum as possible user
> interaction from one IMAP backend to another IMAP backend ?

Uhm...  I don't really think there's any pre-defined command for doing
this?  But I may be wrong.

I'd just enter each group in question, process-mark all the articles and
then move/copy the articles to the other server.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/



  reply	other threads:[~2015-02-13  6:57 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 [this message]
2015-02-13  8:25   ` Erik Colson
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=87egpufgd8.fsf@building.gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    --cc=eco@ecocode.net \
    /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).