From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel,gmane.emacs.multi-tty Subject: Re: Merging multitty Date: Fri, 11 May 2007 21:00:48 +0900 Message-ID: References: <2wmz0iriyj.fsf@fencepost.gnu.org> <87fy65k6eh.fsf@red-bean.com> <853b25lk43.fsf@lola.goethe.zz> <86bqgr3g1h.fsf_-_@lola.quinscape.zz> <4644355E.7070004@gnu.org> <867irf3cjo.fsf@lola.quinscape.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1178884875 21113 80.91.229.12 (11 May 2007 12:01:15 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 11 May 2007 12:01:15 +0000 (UTC) Cc: karoly@lorentey.hu, emacs-devel@gnu.org, multi-tty@fnord.hu, rms@gnu.org, jasonr@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 11 14:01:12 2007 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.50) id 1HmTo7-0002D6-RX for ged-emacs-devel@m.gmane.org; Fri, 11 May 2007 14:01:12 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HmTvX-0003x9-3v for ged-emacs-devel@m.gmane.org; Fri, 11 May 2007 08:08:51 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HmTvT-0003vp-Ux for emacs-devel@gnu.org; Fri, 11 May 2007 08:08:48 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HmTvQ-0003tq-RD for emacs-devel@gnu.org; Fri, 11 May 2007 08:08:47 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HmTvQ-0003tn-Ov for emacs-devel@gnu.org; Fri, 11 May 2007 08:08:44 -0400 Original-Received: from mx1.aist.go.jp ([150.29.246.133]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HmTns-0002QD-Js; Fri, 11 May 2007 08:00:57 -0400 Original-Received: from rqsmtp2.aist.go.jp (rqsmtp2.aist.go.jp [150.29.254.123]) by mx1.aist.go.jp with ESMTP id l4BC0nFR005680; Fri, 11 May 2007 21:00:49 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp4.aist.go.jp by rqsmtp2.aist.go.jp with ESMTP id l4BC0nGF025878; Fri, 11 May 2007 21:00:49 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp4.aist.go.jp with ESMTP id l4BC0mlo025830; Fri, 11 May 2007 21:00:48 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken.m17n.org with local (Exim 4.63) (envelope-from ) id 1HmTnk-0005PB-BF; Fri, 11 May 2007 21:00:48 +0900 In-reply-to: <867irf3cjo.fsf@lola.quinscape.zz> (message from David Kastrup on Fri, 11 May 2007 12:00:27 +0200) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/23.0.0 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) X-detected-kernel: Solaris 8 (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:70802 gmane.emacs.multi-tty:681 Archived-At: In article <867irf3cjo.fsf@lola.quinscape.zz>, David Kastrup writes: > So yes, I am aware that multitty will likely destabilize the trunk and > require work until the trunk is useful on all architectures again. At least, merging unicode-2 doesn't make the trunk unuseful for any architecture, so I think it must be the first. It may cause some problem, but it is just because that part is not yet tested by any of unicode-2 users. Once the problem is reported, I think I can fix it quite soon. Currently Miles is synchronizing unicode-2 to the trunk periodically (great thanks for that effort). If we merge multitty to the trunk at first, and make the trunk unuseful for some architecture, unicode-2 branch will also be unuseful for that architecture after Miles synchronization, which I do want to avoid. Unicode branch has been there for more than 5 years, and we should think that it is a kind of big bugfix for the current weird/complicated character handling. --- Kenichi Handa handa@m17n.org