From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: Next release Date: Sat, 03 May 2008 17:56:03 -0700 Message-ID: <200805040056.m440u3eS022727@sallyv1.ics.uci.edu> References: <18457.37369.262079.668907@kahikatea.snap.net.nz> <5jr6clncn8.fsf@fencepost.gnu.org> <87od7p22dw.fsf@stupidchicken.com> <200805021331.m42DVYVw016584@sallyv1.ics.uci.edu> <200805021610.m42GAhkE001271@sallyv1.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1209862728 30348 80.91.229.12 (4 May 2008 00:58:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 4 May 2008 00:58:48 +0000 (UTC) Cc: Glenn Morris , Chong Yidong , Nick Roberts , emacs-devel@gnu.org To: YAMAMOTO Mitsuharu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 04 02:59:22 2008 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 1JsSZV-0005dW-OB for ged-emacs-devel@m.gmane.org; Sun, 04 May 2008 02:59:22 +0200 Original-Received: from localhost ([127.0.0.1]:47963 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JsSYo-0001DR-C8 for ged-emacs-devel@m.gmane.org; Sat, 03 May 2008 20:58:38 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JsSYQ-000130-OX for emacs-devel@gnu.org; Sat, 03 May 2008 20:58:14 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JsSYP-00012A-1v for emacs-devel@gnu.org; Sat, 03 May 2008 20:58:14 -0400 Original-Received: from [199.232.76.173] (port=48891 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JsSYO-000120-Ta for emacs-devel@gnu.org; Sat, 03 May 2008 20:58:12 -0400 Original-Received: from sallyv1.ics.uci.edu ([128.195.1.109]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1JsSYF-00055D-G0; Sat, 03 May 2008 20:58:03 -0400 X-ICS-MailScanner-Watermark: 1210467365.02149@tF3h4ho9aE/VxjAkjRRMoQ Original-Received: from mothra.ics.uci.edu (mothra.ics.uci.edu [128.195.6.93]) by sallyv1.ics.uci.edu (8.13.7+Sun/8.13.7) with ESMTP id m440u3eS022727; Sat, 3 May 2008 17:56:04 -0700 (PDT) Original-Lines: 75 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.44, required 5, autolearn=disabled, ALL_TRUSTED -1.44) X-ICS-MailScanner-From: dann@mothra.ics.uci.edu X-detected-kernel: by monty-python.gnu.org: Solaris 10 (beta) 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:96403 Archived-At: YAMAMOTO Mitsuharu writes: > >>>>> On Fri, 02 May 2008 09:10:43 -0700, Dan Nicolaescu said: > > > YAMAMOTO Mitsuharu writes: > >> >>>>> On Fri, 02 May 2008 06:31:34 -0700, Dan Nicolaescu > >> said: > >> > >> > Looking at src/ChangeLog there are pages after pages of changes > >> for > the Mac, which don't look at all like minor changes... > >> > >> You're seeing the changes that have been accumulated for a > >> relatively long period because I restricted the changes between > >> 22.1 and 22.2 to strict bug fixes. > > Correction: not "between 22.1 and 22.2", but "between 22.0.90 and > 22.2". That's why the recent changes include those as of > before-merge-multi-tty-to-trunk. Which is fundamentally different from the stated policy for the branch, unless the mac platform got a special dispense. If it did, it wasn't posted explicitly on the list. Yidong, does this work OK with the goals for the 22 branch? Allow development for the Mac, and only minor bug fixes for the other platforms? Will a quick security fix release work in this scenario? > >> Don't worry. They don't break the Carbon port of Emacs 22 unlike > >> the minimally-tested multi-tty support you've done for the Carbon > >> port of Emacs 23. > > > Thank you, this is a great way to thank someone that is not a user > > of Carbon, does not have experience on that platform, but > > volunteered his time to get it from not even compiling to the point > > where it can start up. And that was the only effort since to get > > this working. Again, thank you very much for your appreciation. > > What was the motivation to do that then? If you were familiar with > either Carbon or multi-tty, I could understand that. Did you want to > pretend as if multi-tty was ready to get merged to the trunk? Thanks again, questioning a gift and bashing the giver is indeed the ideal way to treat the giver. No good deed should ever go unpunished! Congratulation on the great strategy employed here: it is so much better to spend time to periodically whine on the mailing list about the multi-tty merge, and now, out of the blue, abuse _again_ the only person that actually did _anything_ to get Carbon working with multi-tty, when it would be would be much less effort to actually fix the minor bugs left. Outstanding job! This excellent attitude, good manners towards contributors and great interest in the multi-tty work is even more admirable when seen in context: From: YAMAMOTO Mitsuharu Subject: Re: Reordering etc/NEWS Date: Thu, 10 May 2007 19:28:55 +0900 >>>>> On Thu, 10 May 2007 08:24:57 +0100, Jason Rumney said: > That is extremely optimistic. Has anyone even tried the multitty branch > on Mac and Windows yet? I know there is still significant work required > for emacs-unicode-2 on Windows, though it at least basically works. As for Mac, I'm planning to quit the development of the Carbon port for Emacs 23, as the Cocoa/GNUstep port will replace it on that version. So, personally I don't care if multitty is incompatible with the current Carbon code as long as it is not for Emacs 22.x (x > 1). YAMAMOTO Mitsuharu