From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii 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 17:06:12 +0300 Message-ID: <83bnuwebzf.fsf@gnu.org> 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> <20140517083110.GA3398@acm.acm> <83fvk8ep0u.fsf@gnu.org> <87d2fcr0w8.fsf@wanadoo.es> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: ger.gmane.org 1400335609 22758 80.91.229.3 (17 May 2014 14:06:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 17 May 2014 14:06:49 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?iso-8859-1?Q?=D3scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 17 16:06:42 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 1WlfG4-00023R-LQ for ged-emacs-devel@m.gmane.org; Sat, 17 May 2014 16:06:40 +0200 Original-Received: from localhost ([::1]:40270 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WlfG4-0004ZF-3l for ged-emacs-devel@m.gmane.org; Sat, 17 May 2014 10:06:40 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45733) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WlfFl-0004E4-JC for emacs-devel@gnu.org; Sat, 17 May 2014 10:06:28 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WlfFe-0001KD-KC for emacs-devel@gnu.org; Sat, 17 May 2014 10:06:21 -0400 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:44980) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WlfFe-0001K4-DH for emacs-devel@gnu.org; Sat, 17 May 2014 10:06:14 -0400 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0N5Q00L001ODIS00@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Sat, 17 May 2014 17:06:12 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N5Q00LPP1UCHH20@a-mtaout20.012.net.il>; Sat, 17 May 2014 17:06:12 +0300 (IDT) In-reply-to: <87d2fcr0w8.fsf@wanadoo.es> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.166 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:171911 Archived-At: > From: =D3scar Fuentes > Date: Sat, 17 May 2014 15:27:19 +0200 >=20 > from the point of view of those of us that always work with the > cc-mode integrated on the latest Emacs, it would be the obvious > workflow. But for those users and contributors with older Emacs > versions, working with/on the latest cc-mode version would be more > inconvenient. Alan would be inconvenienced too as he has to > develop/test cc-mode against multiple Emacs versions. >=20 > So I guess that merging cc-mode into Emacs (a specific branch of Em= acs, > to be precise) would become very easy, but all the rest would be mo= re > inconvenient, as long as the cc-mode development cares about past E= macs > versions. I obviously won't pursue this any longer, as Alan sounds very much se= t on his current arrangements. But I cannot help wondering how real ar= e all those considerations you mentioned, given that major CC Mode releases are relatively infrequent, on par with those of Emacs. IMO, both separate unsynchronized development and trying to cater to older Emacs versions only make sense if a package is being released much more frequently than the Emacs core. Otherwise, it's pure overhead and waste of valuable resources, since in practice no one has any goo= d reasons to use a newer CC Mode with an old Emacs. The same goes for Gnus, FWIW (which AFAICS no longer provides its own stable releases anyway), which Alan mentioned as another package with similar mode of development. Now, I'm sure a plethora of arguments will follow that would "explain= " why bringing all development to a single repo is not TRT, from the PO= V of the developers of the corresponding packages. But I'm also quite sure all these arguments are not serious enough to justify the terrible waste of time and energy we as a community suffer as the result of these schisms.