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: Post-22.1 development? Date: Tue, 05 Jun 2007 23:13:02 +0200 Message-ID: <85ps4ap0kh.fsf@lola.goethe.zz> References: <878xb05ras.fsf@stupidchicken.com> <864plnorgn.fsf@lola.quinscape.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1181077998 20605 80.91.229.12 (5 Jun 2007 21:13:18 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 5 Jun 2007 21:13:18 +0000 (UTC) Cc: cyd@stupidchicken.com, rms@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 05 23:13:16 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 1HvgL5-0001mK-Hz for ged-emacs-devel@m.gmane.org; Tue, 05 Jun 2007 23:13:15 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HvgL4-00036V-T0 for ged-emacs-devel@m.gmane.org; Tue, 05 Jun 2007 17:13:14 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HvgL1-00036Q-2C for emacs-devel@gnu.org; Tue, 05 Jun 2007 17:13:11 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HvgKx-00036D-F0 for emacs-devel@gnu.org; Tue, 05 Jun 2007 17:13:10 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HvgKx-00036A-CM for emacs-devel@gnu.org; Tue, 05 Jun 2007 17:13:07 -0400 Original-Received: from mail-in-07.arcor-online.net ([151.189.21.47]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HvgKv-0007sU-7o; Tue, 05 Jun 2007 17:13:05 -0400 Original-Received: from mail-in-01-z2.arcor-online.net (mail-in-09-z2.arcor-online.net [151.189.8.21]) by mail-in-07.arcor-online.net (Postfix) with ESMTP id 8C08C24B601; Tue, 5 Jun 2007 23:13:03 +0200 (CEST) Original-Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net [151.189.21.41]) by mail-in-01-z2.arcor-online.net (Postfix) with ESMTP id 0ED7728EBD4; Tue, 5 Jun 2007 23:13:03 +0200 (CEST) Original-Received: from lola.goethe.zz (dslb-084-061-057-235.pools.arcor-ip.net [84.61.57.235]) by mail-in-01.arcor-online.net (Postfix) with ESMTP id C22791B326D; Tue, 5 Jun 2007 23:13:02 +0200 (CEST) Original-Received: by lola.goethe.zz (Postfix, from userid 1002) id 3472B1C2FE53; Tue, 5 Jun 2007 23:13:02 +0200 (CEST) In-Reply-To: (Eli Zaretskii's message of "Tue\, 05 Jun 2007 22\:54\:16 +0300") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1.50 (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:72294 Archived-At: Eli Zaretskii writes: >> From: David Kastrup >> Date: Tue, 05 Jun 2007 08:17:28 +0200 >> Cc: Eli Zaretskii , cyd@stupidchicken.com, emacs-devel@gnu.org >> >> Richard Stallman writes: >> >> > FWIW, I don't think we should merge changes that are safe until >> > some time has passed and we have some kind of idea about how >> > buggy v22.1 is. If the number of problems we hear on >> > bug-gnu-emacs is large, then we should stabilize 22.x before we >> > merge changes that can potentially destabilize it. >> > >> > We need to see, first of all, how many problems are reported in >> > 22.1. >> >> Why do we need to see that? Problems in 22.1 will be of two kinds: >> >> a) Problems that have a better fix or solution in Emacs 23 >> b) Problems that have the same fix or solution in Emacs 23 > > In case it wasn't clear, _I_ was talking about merging changes to the > EMACS_22_BASE branch, not to the trunk. Hm, I was of the opinion that the topic of the thread was the question what is keeping us from merging unicode-2 into the trunk. Richard suggested that we wanted to keep the trunk close to EMACS_22_BASE for several months. I protested, and Jason said that if there were things in the trunk intended for 22.2, we should merge them into EMACS_22_BASE now so that the trunk is free for getting unicode-2 merged into it. And Jason said that 22.2-relevant fixes/changes should then happen in EMACS_22_BASE and possibly be merged back into the trunk. I disagree here, actually: I'd start all fixes that make sense in 23.1 in the trunk. Merging them into EMACS_22_BASE would remain the responsibility of the people interested on working on EMACS_22_BASE (it would be the job of the Emacs 22 maintainer, whether or not that is the same person as the trunk maintainer, to check stuff regularly and nag people about putting them into EMACS_22_BASE if he thinks this desirable). Anyway, this is a detail where Jason and I have different opinions. Sure, accepting Richard's suggestion that we should keep trunk parallel to EMACS_22_BASE and have a _separate_ unicode-2 for some months, leads to the question whether to put Emacs 22.2 development first into EMACS_22_BASE and then copy to the trunk, or the other way round. But I consider it a mistake to even ponder this question: when the plan is to keep them identical, we don't need two branches for that. It is just a nonsensical duplication of effort, and whether we copy from A to B or from B to A while keeping A and B identical is just smokescreen over the fact that we don't need both A and B if we intend to keep them the same. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum