From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.137.132 with SMTP id w4cs71411bkt; Sun, 11 Apr 2010 17:57:52 -0700 (PDT) Received: by 10.204.127.70 with SMTP id f6mr3861284bks.76.1271033872700; Sun, 11 Apr 2010 17:57:52 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 1si8991580bky.81.2010.04.11.17.57.52; Sun, 11 Apr 2010 17:57:52 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 0F7891D799CA; Sun, 11 Apr 2010 20:57:52 -0400 (EDT) Received: from pion.club.cc.cmu.edu (PION.CLUB.CC.cmu.edu [128.237.157.88]) by rubyforge.org (Postfix) with ESMTP id 92A891858267 for ; Sun, 11 Apr 2010 20:57:44 -0400 (EDT) Received: from rlane by pion.club.cc.cmu.edu with local (Exim 4.69) (envelope-from ) id 1O17yA-0002Pw-TY; Sun, 11 Apr 2010 20:57:42 -0400 From: Rich Lane To: Ryan Barrett In-reply-to: References: Date: Sun, 11 Apr 2010 20:57:42 -0400 Message-Id: <1271023429-sup-9851@zyrg.net> User-Agent: Sup/git Cc: sup-talk , sjh Subject: Re: [sup-talk] current state of synching upstream? X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Ryan Barrett's message of 2010-04-08 05:40:32 -0400: > 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. My primary goal for the 0.12 release is making Sup play nice with other clients. You can see the work in progress on the maildir branch - it's getting more stable but it's still rough around the edges. Most of the changes on this branch are to make Sup gracefully handle cases where another client has moved or deleted mail out from under us. Sup will automatically detect changes to the Seen flag in the maildir and update the message's labels. I haven't decided what to do about the other direction. Historically Sup has never modified mail sources, but changing flags in a maildir is safe enough that I might implement it. Running sup-sync-back has the problem that you can't run the UI at the same time. Does anyone use the current sup-sync-back that only support mboxes? If there are no strong objections then the 0.12 sup-sync-back will only support maildir. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk