From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: moving from nnml to nnimap
Date: Tue, 15 Mar 2011 11:07:18 -0500 [thread overview]
Message-ID: <87pqps2wqx.fsf@lifelogs.com> (raw)
In-Reply-To: <m3tyf4jryv.fsf@quimbies.gnus.org>
On Tue, 15 Mar 2011 16:58:32 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> It's extremely likely to get interrupted, though. So really what you
>> want is something like imapsync but for Gnus.
LMI> Yes. But it should be possible to keep track of what's been copied
LMI> over, so that the copying process can be restarted when it (inevitably)
LMI> fails. So it'll have to be implemented carefully, but it would be
LMI> useful.
>> Perhaps that's better left as a Cloudy Gnus TODO item.
LMI> It's kinda orthogonal to the Cloudy functionality...
I don't mean it will be "cloudy" functionality, only that it's major
enough that I'd like to do it after No Gnus is released.
Ted
P.S. Ha ha! I've got you saying "Cloudy Gnus" too!
next prev parent reply other threads:[~2011-03-15 16:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 19:55 Randal L. Schwartz
2011-03-14 20:11 ` Ted Zlatanov
2011-03-15 1:02 ` Dave Goldberg
2011-03-15 15:28 ` Lars Magne Ingebrigtsen
2011-03-15 15:51 ` Ted Zlatanov
2011-03-15 15:58 ` Lars Magne Ingebrigtsen
2011-03-15 16:07 ` Ted Zlatanov [this message]
2011-03-15 16:13 ` Lars Magne Ingebrigtsen
2011-03-17 8:13 ` Reiner Steib
2011-03-17 14:46 ` Ted Zlatanov
2011-03-17 19:07 ` Randal L. Schwartz
2011-03-17 19:15 ` Lars Magne Ingebrigtsen
2011-03-17 20:17 ` Randal L. Schwartz
2011-03-17 20:19 ` Lars Magne Ingebrigtsen
2011-03-17 22:12 ` Randal L. Schwartz
2011-03-29 19:12 ` Lars Magne Ingebrigtsen
2011-03-16 8:38 ` Steinar Bang
2011-03-16 13:55 ` Ted Zlatanov
2011-03-17 8:12 ` Steinar Bang
2011-03-17 10:58 ` Ted Zlatanov
-- strict thread matches above, loose matches on Subject: below --
2003-11-24 0:59 Moving " Jinhyok Heo
2003-11-24 1:48 ` Daniel Pittman
2003-11-24 16:24 ` Ted Zlatanov
2003-11-25 17:01 ` Ken Raeburn
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=87pqps2wqx.fsf@lifelogs.com \
--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).