From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Monnier Subject: Re: Sync up the org in emacs master to org maint branch? Date: Thu, 02 Feb 2017 09:50:58 -0500 Message-ID: References: <87k29d7zvw.fsf@engster.org> <87fuk08i01.fsf@engster.org> <87d1f36xnc.fsf@engster.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sender: "Emacs-devel" To: emacs-devel@gnu.org Cc: emacs-orgmode@gnu.org List-Id: emacs-orgmode.gnu.org > In fact, what we're doing feels like if Python included Django in its main > repository, just to solve Django's problems of compatibility, testing, and > making its bugs known to the main Python developers. No: the reason CEDET is inside Emacs is double: 1- We wanted to make CEDET's features available to more users. 2- We wanted to integrate it more tightly with Emacs (not in terms of bug-tracking and releasing schedule, but in terms of making it possible for generic Emacs code to use some of CEDET, and to encourage more major modes and other features to use CEDET). Moving all of CEDET to elpa.git (and then including it in the tarball) would still get us point nb 1 but not point nb 2. The main problem so far with CEDET is the "two branches" situation, made worse by the "time-limited" copyright assignment of Eric. I'm not sure what's going on w.r.t the Eric's copyright assignment, but if that problem is still with us, then it will plague CEDET-in-elpa just as much as it did CEDET-in-emacs. I think the main plan should be to consolidate the development into a single branch (of course, that can also be several branches, as long as they are constantly kept in sync). The easiest would be to have that "upstream" be in emacs.git for now (since moving Emacs's CEDET outside of Emacs would likely take time anyway). It might also be beneficial to move some of CEDET to elpa.git (those features which aren't "core" and are hence unlikely to be used by other parts of Emacs), so their development can be decoupled. But I think CEDET-core (such as lisp/cedet/semantic) should stay in emacs.git (and more packages should make use of it). Stefan