From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: unicode-2 and multitty Date: Fri, 04 May 2007 12:14:23 +0200 Message-ID: <86r6pw28w0.fsf@lola.quinscape.zz> References: <87647ooxwm.fsf@zip.com.au> <462CC030.8030203@gmail.com> <87mz0y8vyk.fsf@zip.com.au> <86vef90x54.fsf_-_@lola.quinscape.zz> <463AFFC9.90307@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1178273681 14228 80.91.229.12 (4 May 2007 10:14:41 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 4 May 2007 10:14:41 +0000 (UTC) Cc: emacs-devel@gnu.org To: Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 04 12:14:38 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 1Hjuo4-00062E-H8 for ged-emacs-devel@m.gmane.org; Fri, 04 May 2007 12:14:32 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hjuug-0007Dt-Qa for ged-emacs-devel@m.gmane.org; Fri, 04 May 2007 06:21:22 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hjuue-0007Do-9W for emacs-devel@gnu.org; Fri, 04 May 2007 06:21:20 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hjuub-0007Dc-II for emacs-devel@gnu.org; Fri, 04 May 2007 06:21:19 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hjuub-0007DZ-Ez for emacs-devel@gnu.org; Fri, 04 May 2007 06:21:17 -0400 Original-Received: from pc3.berlin.powerweb.de ([62.67.228.11]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Hjuny-00039o-4A for emacs-devel@gnu.org; Fri, 04 May 2007 06:14:26 -0400 Original-Received: from quinscape.de (pd95b0fdb.dip0.t-ipconnect.de [217.91.15.219]) by pc3.berlin.powerweb.de (8.9.3p3/8.9.3) with ESMTP id MAA17856 for ; Fri, 4 May 2007 12:14:21 +0200 X-Delivered-To: Original-Received: (qmail 10005 invoked from network); 4 May 2007 10:14:23 -0000 Original-Received: from unknown (HELO lola.quinscape.zz) ([10.0.3.43]) (envelope-sender ) by ns.quinscape.de (qmail-ldap-1.03) with SMTP for ; 4 May 2007 10:14:23 -0000 Original-Received: by lola.quinscape.zz (Postfix, from userid 1001) id 55B238F95C; Fri, 4 May 2007 12:14:23 +0200 (CEST) In-Reply-To: <463AFFC9.90307@gnu.org> (Jason Rumney's message of "Fri\, 04 May 2007 10\:41\:29 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.91 (gnu/linux) X-detected-kernel: Linux 2.4-2.6 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:70538 Archived-At: Jason Rumney writes: > David Kastrup wrote: >> I know that there are a few prepacked "Emacs-23" variants around: >> would it be acceptable to the maintainers of those if the unicode-2 >> branch were to go through a period of relative instability caused by >> the merge of multitty? >>=20=20=20 > > Since multitty has never been in CVS, it hasn't had as widespread > testing as unicode-2, especially on non-unix/GNU platforms. So it is > probably better to create a new branch, and first import the multitty > code from its current repository, then merge in the unicode-2 > changes. Once that branch is stable, we can abandon the unicode-2 > branch and use the new branch for all "future" development. Since the file structure of the multitty branch supposedly will see no further changes, an import into CVS will probably not make development harder. K=E1roly, do you think you could create a branch and do that with an updated version of the multitty stuff? There is probably little sense in importing your personal change history. Since the goal after the multitty merge would be merging unicode-2, it would likely make sense to name the branch multitty-unicode-2. Since this step would more or less imply a bit of passing of responsibility for the multitty work, this basically makes sense only if there is a non-zero number of developers who would be willing to spend the time necessary for occasionally synching to HEAD while HEAD still changes (as long as HEAD does not diverge from the release branch, this should not be too much work, and once it is allowed to substantially diverge, it would be time to replace it by the multitty-unicode-2 branch, anyway). There will also be the one-time work to merge unicode-2 into it. Since both multitty and unicode-2 are currently close to HEAD and the functional overlap of the branches is small, the initial merge should likely not require an overwhelming amount of manual work. Getting the merge to actually work might be a different thing, however. It is likely that people (like myself) who have grown accustomed to using their CVS version of Emacs also for production work will have to keep a binary from the HEAD branch around for a while until the merge has converged to a reasonably compilable and crash-free state. But I think this should be doable. It also does not appear to me like the pace of the Emacs 22.1 release would be significantly affected by this diversion of developers moving to a new branch. >>From a project management point of view, it could possibly make more sense to actually do this work in HEAD. While I personally consider the point of the release branching to have been that HEAD can move on to the next development phase, this will be Richard's call to make. Creating a separate multitty-unicode-2 branch leaves open the choice when to move the HEAD attention (usually the principal focus of developer interest) to the remaining Emacs 23 work. --=20 David Kastrup