From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Michael Reilly Newsgroups: gmane.emacs.devel Subject: Re: Rmail-mbox branch Date: Mon, 30 Jun 2008 13:48:49 -0400 Message-ID: <48691C81.7000102@pajato.com> References: <87zlprvod0.fsf@stupidchicken.com> <4868CF84.1040005@pajato.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1214848180 14208 80.91.229.12 (30 Jun 2008 17:49:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 30 Jun 2008 17:49:40 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 30 19:50:26 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KDNW0-0005uC-44 for ged-emacs-devel@m.gmane.org; Mon, 30 Jun 2008 19:50:12 +0200 Original-Received: from localhost ([127.0.0.1]:54188 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KDNV9-0005YK-DD for ged-emacs-devel@m.gmane.org; Mon, 30 Jun 2008 13:49:19 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KDNV4-0005Y6-BJ for emacs-devel@gnu.org; Mon, 30 Jun 2008 13:49:14 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KDNV1-0005Xq-U1 for emacs-devel@gnu.org; Mon, 30 Jun 2008 13:49:13 -0400 Original-Received: from [199.232.76.173] (port=36613 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KDNV1-0005Xn-QH for emacs-devel@gnu.org; Mon, 30 Jun 2008 13:49:11 -0400 Original-Received: from 68-191-253-210.static.oxfr.ma.charter.com ([68.191.253.210]:54499 helo=copa.pajato.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KDNV1-0007WC-HE for emacs-devel@gnu.org; Mon, 30 Jun 2008 13:49:11 -0400 Original-Received: from [127.0.0.1] (copa.pajato.com [68.191.253.210]) (authenticated bits=0) by copa.pajato.com (8.14.1/8.13.8) with ESMTP id m5UHn2UA010394 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 30 Jun 2008 13:49:06 -0400 User-Agent: Thunderbird 2.0.0.14 (X11/20080501) In-Reply-To: X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (copa.pajato.com [68.191.253.210]); Mon, 30 Jun 2008 13:49:06 -0400 (EDT) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:100234 Archived-At: Stefan Monnier wrote: >> In any case, to head off more branch and merge grief, right now I'm >> considering taking an approach of doing a minimalist clone of the mbox >> code to my CVS trunk based workspace and call it Pmail for lack of a >> better name. The goal is to allow me to work on both Rmail/babyl and >> Rmail/mbox simultaneously. It might seem like more work but I have a >> strong hunch that being able to work on both versions side by side >> will help increase the chance that this project will actually get >> done. > > You mean you want to replace the branch by combining both features so > they coexist in the same branch (e.g. in the trunk)? Correct. Once both Rmail/mbox and Rmail/bably are running in the trunk the branch is obsolete. > That sounds like a good plan. Even better if you can avoid duplicating > files, using (if rmail-mbox ) where > necessary instead. This type of approach may make it more difficult (but not impossible by any stretch) to have both running simultaneously. I'll keep it in mind. The more I think about it the more appealing it is. > As long as the BABYL code is not broken before the mbox code works, and > as long as there is clear understanding that we *will* finish the mbox > support, you could even install this code on the trunk so people can > test it just by (setq rmail-mbox t). Agreed. -pmr