From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!not-for-mail
From: Jason Rumney <jasonr@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: Carbon port emacs-unicode-2 build problem under MacOSX
Date: Wed, 07 Nov 2007 15:05:35 +0000
Message-ID: <4731D43F.3060007@gnu.org>
References: <m21wb3vayb.fsf@news.cyberhut.org>
	<47305F6E.2030204@gnu.org>	<m2fxzjw4xu.fsf@lifelogs.com>
	<loom.20071107T111446-237@post.gmane.org>
NNTP-Posting-Host: lo.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Trace: ger.gmane.org 1194447994 12813 80.91.229.12 (7 Nov 2007 15:06:34 GMT)
X-Complaints-To: usenet@ger.gmane.org
NNTP-Posting-Date: Wed, 7 Nov 2007 15:06:34 +0000 (UTC)
Cc: emacs-devel@gnu.org
To: Adrian Robert <Adrian.B.Robert@gmail.com>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 07 16:06:36 2007
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
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 1IpmU3-0002Qs-5K
	for ged-emacs-devel@m.gmane.org; Wed, 07 Nov 2007 16:06:23 +0100
Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43)
	id 1IpmTs-000212-0Z
	for ged-emacs-devel@m.gmane.org; Wed, 07 Nov 2007 10:06:12 -0500
Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IpmTQ-0001mN-4N
	for emacs-devel@gnu.org; Wed, 07 Nov 2007 10:05:44 -0500
Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IpmTO-0001ju-8Q
	for emacs-devel@gnu.org; Wed, 07 Nov 2007 10:05:43 -0500
Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IpmTO-0001ji-1U
	for emacs-devel@gnu.org; Wed, 07 Nov 2007 10:05:42 -0500
Original-Received: from outmail1.freedom2surf.net ([194.106.33.237])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <jasonr@gnu.org>) id 1IpmTM-0005uw-BY
	for emacs-devel@gnu.org; Wed, 07 Nov 2007 10:05:40 -0500
Original-Received: from [127.0.0.1] (host81-149-25-51.in-addr.btopenworld.com
	[81.149.25.51]) by outmail1.freedom2surf.net (Postfix) with ESMTP
	id 983DE509D0; Wed,  7 Nov 2007 15:05:39 +0000 (GMT)
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
In-Reply-To: <loom.20071107T111446-237@post.gmane.org>
X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=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:82745
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/82745>

Adrian Robert wrote:
> I was planning to ask about inclusion after finishing up the multi-tty
> integration.  But anyway since the issue has been raised, is autumn 2007 a good
> time to consider merging the Cocoa/GNUstep port into the unicode-2 branch, or
> would people prefer to wait until after unicode-2 -> trunk?  Based on my
> experiences, the latter approach would be much less headache, but don't know how
> far off the unicode merge is at the moment.
>   


I'd suggest the following timetable.

1. Start the 22.2 pretest (hopefully a short pretest cycle).
2. Release 22.2 without getting distracted by more merges.
3. Merge unicode-2 to the trunk (I think it is ready now, so immediately
after 22.2 release would be good).
4. Merge Cocoa port (if 22.2 pretest starts taking a long time though,
it might be better to merge to unicode-2 earlier).
5. Enable new font-backend by default.
6. Remove the old font code (which unless someone implements a backend
for Carbon, implies the end of the Carbon port)