From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.101.196 with SMTP id fi4cs24146vdb; Mon, 11 Apr 2011 14:47:13 -0700 (PDT) Received: by 10.229.127.96 with SMTP id f32mr4547188qcs.139.1302558432923; Mon, 11 Apr 2011 14:47:12 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id q12si11574024qcu.37.2011.04.11.14.47.12; Mon, 11 Apr 2011 14:47:12 -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 728A31858363; Mon, 11 Apr 2011 17:47:12 -0400 (EDT) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by rubyforge.org (Postfix) with SMTP id 4E2161858112 for ; Mon, 11 Apr 2011 17:44:54 -0400 (EDT) Received: (qmail invoked by alias); 11 Apr 2011 21:44:53 -0000 Received: from hmbg-5f76419a.pool.mediaWays.net (EHLO localhost) [95.118.65.154] by mail.gmx.net (mp019) with SMTP; 11 Apr 2011 23:44:53 +0200 X-Authenticated: #67991182 X-Provags-ID: V01U2FsdGVkX1/+gVN2+D3+3TkUF85KISLQMt4t8+EUHkF1XPXey3 2DRI8/yScpyuoR From: dtk To: Damien Leone In-reply-to: <1302513523-sup-904@mailer> References: <1302508168-sup-3103@minibox> <1302513523-sup-904@mailer> Date: Mon, 11 Apr 2011 23:44:51 +0200 Message-Id: <1302557683-sup-109@minibox> User-Agent: Sup/0.12.1 X-Y-GMX-Trusted: 0 Cc: sup-talk Subject: Re: [sup-talk] Maildir support 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 Hi Damien, Excerpts from Damien Leone's message of Mon Apr 11 11:22:09 +0200 2011: > By default sup doesn't modify the sources at all. why is that? I thought the way a MUA is supposed to work with a maildir is rather straight forward[0]? > There is a branch > that allows backward synchronization, you will find more informations > at the following address: > > http://www.mail-archive.com/sup-devel@rubyforge.org/msg00983.html Thanks for the hint!! I am a bit suspicious, though :| I don't know much about git, but doesn't that essentially mean that the branch is always stuck behind the features in master until the new features have manually been merged in? And that for every release of master a manual release of the 'maildir' branch has to be made? Additionally, I consider this a very basic feature. What happens, if there is another basic feature that is maintained in _another_ branch? How will I ever be able to use them together? You know, I'm just wondering why this feature isn't merged in upstream. Are there any reasons why anyone would _not_ want proper maildir handling? Or is this just a political decision (scared, since I've seen a few of those pull down cool projects :/)? Anyway, thanks for your fast reply! dtk ---------- [0]http://en.wikipedia.org/wiki/Maildir#Technical_operation _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk