Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Ryan Barrett <sup-talk@ryanb.org>
To: sup-talk@rubyforge.org
Cc: sjh@foolishpride.org
Subject: [sup-talk] current state of synching upstream?
Date: Thu, 8 Apr 2010 02:40:32 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.1004080235530.8539@snarfed.org> (raw)

hi all! i've been looking forward to trying sup since i first heard about it a 
couple years ago, and i'm getting pretty close. one of my few remaining 
concerns is using sup in parallel with other mail clients, including sup 
itself.

i know best practice is to just use one sup installation and no other clients, 
but i also know that synching back upstream is a frequent topic here. i've seen 
the discussions of sup-sync --changed, sup-sync-back, maildir + offlineimap 
etc. i'm mostly looking to hear about the current state. is anyone 
successfully running sup synched with another sup or other client? if so, how?

it seems like people have generally agreed that the best approach is to make 
sup-sync-back support maildir, and then use offlineimap to sync from maildir 
to the source. is that still true? cc'ing scott henson, who mentioned he was 
working on maildir sync in january.

http://rubyforge.org/pipermail/sup-talk/2010-January/003761.html

more background:

http://rubyforge.org/pipermail/sup-talk/2009-April/002126.html

http://rubyforge.org/pipermail/sup-talk/2009-July/002567.html

-Ryan

--
http://snarfed.org/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


             reply	other threads:[~2010-04-08 10:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  9:40 Ryan Barrett [this message]
2010-04-11 17:52 ` Ryan Barrett
2010-04-12  0:57 ` Rich Lane
2010-04-12  5:02   ` Andrew Pimlott
2010-04-12 12:11     ` Daemian Mack
2010-04-12  9:53   ` Tero Tilus
2010-04-14 13:00   ` William Morgan
2010-04-14 14:16     ` Ben Walton
2010-04-14 15:57       ` William Morgan
2010-04-14 16:08         ` Ben Walton
2010-12-15  8:19           ` Matthias Vallentin
2010-12-15 17:06             ` James Taylor
2010-12-18  5:12               ` Matthias Vallentin
2010-12-18  5:25                 ` James Taylor
2010-12-18 19:04                   ` Matthias Vallentin
2010-12-18 19:21                     ` Ben Walton
2010-12-18 20:02                       ` Tero Tilus
2010-12-18 20:12                         ` Ben Walton
2010-12-21  6:44                       ` Matthias Vallentin
2010-12-21  6:48                         ` Matthias Vallentin
2010-12-21 11:01                         ` Tero Tilus
2010-12-21 14:11                           ` Ben Walton
2010-12-22 14:42                             ` Matthias Vallentin
2010-12-22 16:27                               ` Tero Tilus

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=Pine.LNX.4.64.1004080235530.8539@snarfed.org \
    --to=sup-talk@ryanb.org \
    --cc=sjh@foolishpride.org \
    --cc=sup-talk@rubyforge.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