From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] support a few of the new features of C++11 in syntax highlighting Date: Sat, 17 May 2014 08:31:10 +0000 Message-ID: <20140517083110.GA3398@acm.acm> References: <536F1D36.6010307@gmail.com> <87ppjks3th.fsf@wanadoo.es> <87lhu8rrtm.fsf@wanadoo.es> <20140511220947.GD2759@acm.acm> <87ha4wrle6.fsf@wanadoo.es> <20140514201353.GA4125@acm.acm> <20140516160743.GA3267@acm.acm> <83sio9ehaf.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1400315752 9527 80.91.229.3 (17 May 2014 08:35:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 17 May 2014 08:35:52 +0000 (UTC) Cc: ofv@wanadoo.es, monnier@IRO.UMontreal.CA, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 17 10:35:45 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Wla5k-0007I1-Et for ged-emacs-devel@m.gmane.org; Sat, 17 May 2014 10:35:40 +0200 Original-Received: from localhost ([::1]:39236 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wla5j-0007Uj-KB for ged-emacs-devel@m.gmane.org; Sat, 17 May 2014 04:35:39 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53377) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wla5b-0007Ql-Br for emacs-devel@gnu.org; Sat, 17 May 2014 04:35:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wla5V-0000Ro-0j for emacs-devel@gnu.org; Sat, 17 May 2014 04:35:31 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:32310 helo=mail.muc.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wla5U-0000RV-Ht for emacs-devel@gnu.org; Sat, 17 May 2014 04:35:24 -0400 Original-Received: (qmail 82214 invoked by uid 3782); 17 May 2014 08:35:21 -0000 Original-Received: from acm.muc.de (pD951B643.dip0.t-ipconnect.de [217.81.182.67]) by colin.muc.de (tmda-ofmipd) with ESMTP; Sat, 17 May 2014 10:35:20 +0200 Original-Received: (qmail 3444 invoked by uid 1000); 17 May 2014 08:31:10 -0000 Content-Disposition: inline In-Reply-To: <83sio9ehaf.fsf@gnu.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Delivery-Agent: TMDA/1.1.12 (Macallan) X-Primary-Address: acm@muc.de X-detected-operating-system: by eggs.gnu.org: FreeBSD 8.x X-Received-From: 193.149.48.1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:171904 Archived-At: Hello, Eli. On Fri, May 16, 2014 at 08:59:20PM +0300, Eli Zaretskii wrote: > > Date: Fri, 16 May 2014 16:07:43 +0000 > > From: Alan Mackenzie > > Cc: Óscar Fuentes , emacs-devel@gnu.org > > > I'm curious: how did we get to this point? > > We've never been anywhere else. CC Mode developement has always taken > > place mainly in its own project at SourceForge. > Then I guess the question is "why keep doing that?" IOW, why not > develop it as part of Emacs? CC Mode also feeds into XEmacs. This would be more difficult to do if CC Mode were an integrated part of Emacs rather than being independent of both. There are distinct advantages with working with a small code base on a stable base (a released version of Emacs) as compared with being in the thick of a "major war" (an upcoming version of Emacs, which doesn't even build all the time). Presumably other upstream projects like Gnus, Cedet, are distinct from Emacs for similar reasons. > > > Shouldn't such development take place on trunk, or a branch that's > > > regularly sync'd with Emacs's trunk? > > Absolutely not. That would risk having incoherent code automatically > > transferred to Emacs. > You can always use a public branch as part of the Emacs repository, > "cc-mode-unstable", say, and merge from it to trunk when you see fit. > Then this issue won't exist. -- Alan Mackenzie (Nuremberg, Germany).