From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: Merging multitty Date: Fri, 11 May 2007 23:34:24 +0900 Message-ID: <87odkrxwcv.fsf@catnip.gol.com> References: <87fy65k6eh.fsf@red-bean.com> <853b25lk43.fsf@lola.goethe.zz> <86bqgr3g1h.fsf_-_@lola.quinscape.zz> <4644355E.7070004@gnu.org> <867irf3cjo.fsf@lola.quinscape.zz> <86mz0b1p02.fsf@lola.quinscape.zz> <861whn1n9t.fsf@lola.quinscape.zz> Reply-To: Miles Bader NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1178894123 22423 80.91.229.12 (11 May 2007 14:35:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 11 May 2007 14:35:23 +0000 (UTC) Cc: Juanma Barranquero , Kenichi Handa , emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 11 16:35:22 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 1HmWDF-0001iJ-24 for ged-emacs-devel@m.gmane.org; Fri, 11 May 2007 16:35:17 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HmWKf-0002Ma-DA for ged-emacs-devel@m.gmane.org; Fri, 11 May 2007 10:42:57 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HmWJx-0001vs-B9 for emacs-devel@gnu.org; Fri, 11 May 2007 10:42:13 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HmWJw-0001v8-IX for emacs-devel@gnu.org; Fri, 11 May 2007 10:42:12 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HmWJw-0001uw-9G for emacs-devel@gnu.org; Fri, 11 May 2007 10:42:12 -0400 Original-Received: from smtp02.dentaku.gol.com ([203.216.5.72]) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HmWCT-00005O-1S; Fri, 11 May 2007 10:34:29 -0400 Original-Received: from 203-216-99-129.dsl.gol.ne.jp ([203.216.99.129] helo=catnip.gol.com) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1HmWCQ-0002GO-BU; Fri, 11 May 2007 23:34:26 +0900 Original-Received: by catnip.gol.com (Postfix, from userid 1000) id 58EBD2F40; Fri, 11 May 2007 23:34:24 +0900 (JST) System-Type: i686-pc-linux-gnu In-Reply-To: <861whn1n9t.fsf@lola.quinscape.zz> (David Kastrup's message of "Fri\, 11 May 2007 15\:51\:42 +0200") Original-Lines: 38 X-Abuse-Complaints: abuse@gol.com X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) 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:70817 Archived-At: David Kastrup writes: > I would however think it prudent to _first_ have the multitty branch > put into place and synchronized before we do the unicode-2 merge into > the trunk. That will be the best shot we may have at keeping the > multitty branch in a state where its developers have mostly to worry > about multitty issues. > > And it would be good if people familiar with unicode-2 would also help > with merging the trunk change into the multitty branch (since they > probably will best know how to deal with the conflicts). You're right that probably the first thing to do is make a multi-tty branch in the emacs arch/CVS repository. Then at least it becomes easy to find and use by developers (and easily kept synced by us), and the platform maintainers can check it out and maybe do some porting work on it. If it seems in good shape, we can then merge the unicode branch into the multi-tty branch and see how that turns out (I don't expect too many conflicts to be honest, but who knows...). It's easy to do that periodically afterwards, so it can be kept up to date (with both the unicode branch, and indirectly with the trunk). If there _are_ unicode->multi-tty problems they can be worked on slowly in the multi-tty branch; most importantly, no other important branch will be affected (multi-tty is nice but it's far less important than the unicode branch). So when it comes time to actually merge to the trunk there will be two choices: unicode or multi-tty+unicode (since the multi-tty will contain the unicode branch). The merge should be equally easy, as they will both be periodically synced, so the decision can be based purely on whether the multi-tty stuff is stable enough. If it's decided to only merge the unicode branch to the trunk, the multi-tty branch will be easy to keep up to date, because it will already contain the unicode branch. -Miles -- My spirit felt washed. With blood. [Eli Shin, on "The Passion of the Christ"]