From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.137.132 with SMTP id w4cs92177bkt; Mon, 12 Apr 2010 08:35:19 -0700 (PDT) Received: by 10.115.98.17 with SMTP id a17mr3532361wam.74.1271086517212; Mon, 12 Apr 2010 08:35:17 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 20si980446pwi.10.2010.04.12.08.35.16; Mon, 12 Apr 2010 08:35:17 -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 307DA1858310; Mon, 12 Apr 2010 11:35:15 -0400 (EDT) X-Greylist: delayed 614 seconds by postgrey-1.31 at rubyforge.org; Mon, 12 Apr 2010 08:21:36 EDT Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.125]) by rubyforge.org (Postfix) with ESMTP id B7099185828E for ; Mon, 12 Apr 2010 08:21:36 -0400 (EDT) Received: from hrndva-omtalb.mail.rr.com ([10.128.143.51]) by hrndva-qmta01.mail.rr.com with ESMTP id <20100412121225018.NEXZ29767@hrndva-qmta01.mail.rr.com> for ; Mon, 12 Apr 2010 12:12:25 +0000 X-Authority-Analysis: v=1.1 cv=0UlR9Czu668I0eXMyLHigKWn+OyLjOz56zOl0XCIY6Q= c=1 sm=0 a=--dtCbXV-3AA:10 a=IkcTkHD0fZMA:10 a=3KB+lLcUosiKptVDaA2XRg==:17 a=HUjhYrMXAAAA:8 a=oHJGJK8IUVn1hH24sRkA:9 a=c6uAmtPWxuDjkaR8OnEA:7 a=3FWLCk_XbMYsoseqKn-te0_m5NQA:4 a=QEXdDO2ut3YA:10 a=3KB+lLcUosiKptVDaA2XRg==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.71.59.234 Received: from [74.71.59.234] ([74.71.59.234:53710] helo=daemianmack.com) by hrndva-oedge01.mail.rr.com (envelope-from ) (ecelerity 2.2.2.39 r()) with ESMTP id BD/40-25212-1DD03CB4; Mon, 12 Apr 2010 12:10:58 +0000 Received: by daemianmack.com (nbSMTP-1.00) for uid 1000 daemianmack@gmail.com; Mon, 12 Apr 2010 08:11:01 -0400 (EDT) From: Daemian Mack To: Andrew Pimlott In-reply-to: <1271048365-sup-3959@pimlott.net> References: <1271023429-sup-9851@zyrg.net> <1271048365-sup-3959@pimlott.net> Date: Mon, 12 Apr 2010 08:11:01 -0400 Message-Id: <1271072587-sup-4970@lenin> User-Agent: Sup/git X-Mailman-Approved-At: Mon, 12 Apr 2010 11:34:56 -0400 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 Andrew Pimlott's message of Mon Apr 12 01:02:07 -0400 2010: > Excerpts from Rich Lane's message of Sun Apr 11 17:57:42 -0700 2010: > > 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. > > It wouldn't kill me to lose it, but I use it, and think on principle it > would be better to have an overlap period. I use sup-sync-back with mbox. I agree with Andrew that overlap would be a good thing in principle, though personally speaking, I'll probably take this change as a nudge to convert to maildir. My mbox files get pretty large (~80-100Mb) between sup-sync-backs, and working with those files on my aging mail box (1.6GHz Athlon XP) gets pretty clunky in the meantime. Also looking forward to more interclient operability! Any interest in kicking off a simple usage survey to find out how people are using sup? I'd be really curious to see things like... - the mailstore formats being used - whether most people use sup as their sole MUA or as one of many - how multi-MUA users handle working with multiple clients - the various daily sup workflows in use Might be helpful from a "what's going on out there" roadmap perspective, too. -- http://daemianmack.com/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk