From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.devel Subject: Re: New sync'd branch Date: Thu, 27 Aug 2009 17:52:02 -0400 Message-ID: References: <878wh9qaku.fsf@sphinx.net.ru> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1251409948 19826 80.91.229.12 (27 Aug 2009 21:52:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 27 Aug 2009 21:52:28 +0000 (UTC) Cc: emacs-devel@gnu.org, Dmitry Dzhus , Miles Bader To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 27 23:52:20 2009 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 1MgmtH-00074L-BH for ged-emacs-devel@m.gmane.org; Thu, 27 Aug 2009 23:52:20 +0200 Original-Received: from localhost ([127.0.0.1]:38806 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgmtF-0004fJ-Lg for ged-emacs-devel@m.gmane.org; Thu, 27 Aug 2009 17:52:17 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mgmt8-0004dr-02 for emacs-devel@gnu.org; Thu, 27 Aug 2009 17:52:10 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mgmt4-0004bf-J8 for emacs-devel@gnu.org; Thu, 27 Aug 2009 17:52:09 -0400 Original-Received: from [199.232.76.173] (port=47637 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mgmt3-0004b2-Av for emacs-devel@gnu.org; Thu, 27 Aug 2009 17:52:05 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:32899) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mgmt2-0000WI-Bg for emacs-devel@gnu.org; Thu, 27 Aug 2009 17:52:04 -0400 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1Mgmt0-0005av-5C; Thu, 27 Aug 2009 17:52:02 -0400 X-Spook: benelux LLNL SDI UOP Mantis explosion diwn InfoSec X-Ran: N]WC%/EotOS0R'f=!wa\z+1Lq6*oO9cLP=^xdy}zB7X)}>vG.Z\FW7fGDUd%~E->O'LMmZ X-Hue: magenta X-Attribution: GM User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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:114703 Archived-At: Stefan Monnier wrote: > So I believe we should create a new branch EMACS_23 which will play the > role currently played by the trunk, so the trunk can now be open to more > experimental development (bidi, cpp->autoconf conversion, lexbind, ...), > targetted for Emacs-24. It would be good to always have a place for such experimental things. What's the reason to have two branches EMACS_23 and EMACS_23_1_RC? The latter will be almost entirely unused. Are you holding it in reserve in case 23.2 is needed at short notice, eg for a security issue? > There are some problem with this: > - Changes on the 23 branch need to be sync'd to the trunk. As long as > we haven't switched to Bzr, that means we need Miles to do the sync > for us. Or we sync manually, or someone else volunteers to do it "automatically". > - The 23 branch will not see as much testing any more. I think that's the biggest issue. [milesomatic merging] > You don't seem too enthusiastic. Maybe another option would be to > make the Emacs-24 branch not in CVS but directly in Git (from where it > will be eventually turned into a Bzr branch). Sorry, but that's an idea I have no enthusiasm for. I'm happy to sync my own changes manually between CVS branches, or wait for Bzr (assuming this solves all problems).