From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: Re: Why gnus-sync?
Date: Sun, 6 Mar 2016 20:10:58 +0000 (UTC) [thread overview]
Message-ID: <loom.20160306T210947-249@post.gmane.org> (raw)
In-Reply-To: <87bofpurmb.fsf@lifelogs.com>
Ted Zlatanov <tzz <at> lifelogs.com> writes:
>
> On Fri, 26 Oct 2012 12:25:04 -0400 Dave Abrahams
> <dave <at> boostpro.com> wrote:
>
> DA> So, would I use a local imap mailbox for gnus-sync and let mbsync sync
> DA> it remotely?
>
> When I write it, I'll tell you how it behaves :)
Did that rewrite ever happen?
next prev parent reply other threads:[~2016-03-06 20:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 16:56 Dave Abrahams
2012-10-24 19:37 ` Ted Zlatanov
2012-10-24 20:13 ` Dave Abrahams
2012-10-24 21:43 ` Ted Zlatanov
2012-10-24 22:41 ` Dave Abrahams
2012-10-26 12:06 ` Ted Zlatanov
2012-10-26 16:25 ` Dave Abrahams
2012-10-26 16:26 ` Ted Zlatanov
2012-10-26 16:28 ` Dave Abrahams
2012-10-26 16:32 ` Ted Zlatanov
2012-10-27 14:30 ` Steinar Bang
2012-10-27 14:48 ` Steinar Bang
2012-12-02 16:18 ` Ted Zlatanov
2012-12-03 9:52 ` Steinar Bang
2012-12-10 21:18 ` Steinar Bang
2016-03-06 20:10 ` Dave Abrahams [this message]
2016-03-07 13:37 ` Ted Zlatanov
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=loom.20160306T210947-249@post.gmane.org \
--to=dave@boostpro.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).