From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Eric M. Ludlam" Newsgroups: gmane.emacs.devel Subject: Re: Fwd: CEDET sync Date: Mon, 01 Mar 2010 17:42:42 -0500 Message-ID: <4B8C42E2.3080308@siege-engine.com> References: <86bpf7q3fc.wl%lluis@ginnungagap.pc.ac.upc.edu> <87wrxvyijr.fsf@stupidchicken.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: dough.gmane.org 1267485052 20779 80.91.229.12 (1 Mar 2010 23:10:52 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 1 Mar 2010 23:10:52 +0000 (UTC) Cc: Chong Yidong , =?ISO-8859-1?Q?Llu=EDs?= , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 02 00:10:48 2010 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.69) (envelope-from ) id 1NmElD-0004tj-97 for ged-emacs-devel@m.gmane.org; Tue, 02 Mar 2010 00:10:47 +0100 Original-Received: from localhost ([127.0.0.1]:55421 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NmElC-0003SW-Fb for ged-emacs-devel@m.gmane.org; Mon, 01 Mar 2010 18:10:46 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NmEl6-0003QG-6T for emacs-devel@gnu.org; Mon, 01 Mar 2010 18:10:40 -0500 Original-Received: from [140.186.70.92] (port=37724 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NmEl5-0003OJ-4M for emacs-devel@gnu.org; Mon, 01 Mar 2010 18:10:39 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NmEl4-0006wX-Ic for emacs-devel@gnu.org; Mon, 01 Mar 2010 18:10:38 -0500 Original-Received: from bird.interbax.net ([75.126.100.114]:48646) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NmEl4-0006wR-DR for emacs-devel@gnu.org; Mon, 01 Mar 2010 18:10:38 -0500 Original-Received: (qmail 21016 invoked from network); 1 Mar 2010 16:43:55 -0600 Original-Received: from static-71-184-83-10.bstnma.fios.verizon.net (HELO ?192.168.1.201?) (71.184.83.10) by interbax.net with SMTP; 1 Mar 2010 16:43:55 -0600 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.3a1pre) Gecko/20091222 Shredder/3.1a1pre In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Windows 98 (1) 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:121524 Archived-At: On 03/01/2010 04:27 PM, Stefan Monnier wrote: >>> Questions are: >>> 1) is anybody already doing such a sync? >>> 2) if not, from which date should I start synchronizing changes? >>> >>> I'm not fully aware of which extra changes are required for the synchronization >>> (except for the long name -> subdirectory fix), so directions will be much >>> appreciated. > >> I planned to do a sync after the Emacs 23.2 release branch is made, but >> you are welcome to do it if you like. > > I really don't like that smell. We need to make sure the two code-bases > evolve in-sync, which won't work as long as we keep "gratuitous" > differences between the two (file names and things like that). > > I thought Eric was to incorporate most/all of the changes we made into > his version. If this doesn't take place real soon, it'll become much > too painful to maintain. Indeed, that is my plan. I fear the big merge will make it harder to support older Emacsen and XEmacs, so I wanted to get some sort of stable release out that can finalize that style of CEDET. It's just been slow. Since I don't have a feature freeze or anything, CEDET keeps getting a little better over time, almost without me, while I've been getting test suites up and running against various Emacs flavors. My hope is that this last release I did shows few build/compatibility problems and I can easily just post the last release on CVS, then move on. Last year issues and patches kept coming for a couple months. It's been much slower this time around. Eric