From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.101.196 with SMTP id fi4cs31561vdb; Tue, 12 Apr 2011 01:07:58 -0700 (PDT) Received: by 10.224.203.71 with SMTP id fh7mr2045852qab.210.1302595677967; Tue, 12 Apr 2011 01:07:57 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id f18si12243240qck.75.2011.04.12.01.07.56; Tue, 12 Apr 2011 01:07:56 -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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 908901D7846F; Tue, 12 Apr 2011 04:07:56 -0400 (EDT) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by rubyforge.org (Postfix) with ESMTP id B38F11858363 for ; Tue, 12 Apr 2011 03:34:48 -0400 (EDT) Received: by wwd20 with SMTP id 20so7418294wwd.23 for ; Tue, 12 Apr 2011 00:34:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:content-type:subject:from:to:in-reply-to :references:date:message-id:user-agent:content-transfer-encoding; bh=cVkZVOdJujOQWOnz4bnda1s9DBdfnteWeQXdso+4BAA=; b=cpfaxRVnFEUXWWbD4puOEyZ9ECU8FJ4eJ2AO92GM3Yy3Dny/mCI+AXVjWpp9JfUCfZ EQxoPQMXak2HlyV+jGuDvGvKJV7zbFNhlcnwkmYawnZZQCCWyTra5rZWIQVsYgeGpEkB eKAKHB5TiuRsvVjxGV0+LB1DSh4mewi1TM9XI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=LV5BA6+g8HITPEwDj4y+Csmz56YtPQ6syJs6+HkO2gjpJmgX+z0kI67tHNsCesrSxK zVl93l1LUsDINSDNQx5j6UMwMMkwxdNE3Ud0nbPRL82PYFECtKQB/T2HFU0xKdZ4jy25 o/3yp08EXQpvBd9cFercUAyYr3qevlrhsLzVs= Received: by 10.227.154.12 with SMTP id m12mr6272920wbw.193.1302593688009; Tue, 12 Apr 2011 00:34:48 -0700 (PDT) Received: from localhost (mut38-4-82-233-117-144.fbx.proxad.net [82.233.117.144]) by mx.google.com with ESMTPS id b20sm3843833wbb.16.2011.04.12.00.34.46 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2011 00:34:47 -0700 (PDT) From: Damien Leone To: sup-talk In-reply-to: <1302557683-sup-109@minibox> References: <1302508168-sup-3103@minibox> <1302513523-sup-904@mailer> <1302557683-sup-109@minibox> Date: Tue, 12 Apr 2011 09:34:45 +0200 Message-Id: <1302593225-sup-1657@mailer> User-Agent: Sup/git 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, Excerpts from dtk's message of lun. avril 11 23:44:51 +0200 2011: > why is that? I thought the way a MUA is supposed to work with a maildir is > rather straight forward[0]? Well, yeah, but not sup. :) > 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? I keep the maildir-sync branch up to date. If you want the latest version of sup and the maildir synchronization support then use the branch maildir-sync-next from my repository. > 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? Other features usually get merged faster. > 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 :/)? I think it will be merged for the next version although I didn't have any confirmation from William yet. I don't see any reason why that wouldn't be the case, as you said there are a lot of people interested in this feature. The reason why it is not merged yet is that the code has been finished a few weeks ago and needs some more testing (even if I've been using it for 9 months without trouble as well as other people from this list). -- Damien Leone GPG: 0x82EB4DDF _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk