From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii <eliz@gnu.org> Newsgroups: gmane.emacs.devel Subject: Re: Emacs 23.0.91 pretest Date: Fri, 27 Feb 2009 13:28:21 +0200 Message-ID: <uwsbcp19m.fsf@gnu.org> References: <87tz6i6kug.fsf@cyd.mit.edu> Reply-To: Eli Zaretskii <eliz@gnu.org> NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1235734127 15333 80.91.229.12 (27 Feb 2009 11:28:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 27 Feb 2009 11:28:47 +0000 (UTC) Cc: emacs-devel@gnu.org To: Chong Yidong <cyd@stupidchicken.com> Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 27 12:30:03 2009 Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org> 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 1Ld0up-0004tq-K3 for ged-emacs-devel@m.gmane.org; Fri, 27 Feb 2009 12:30:03 +0100 Original-Received: from localhost ([127.0.0.1]:33998 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ld0tU-0004WP-OS for ged-emacs-devel@m.gmane.org; Fri, 27 Feb 2009 06:28:40 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ld0tC-0004Qh-6R for emacs-devel@gnu.org; Fri, 27 Feb 2009 06:28:22 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ld0tA-0004Q4-VF for emacs-devel@gnu.org; Fri, 27 Feb 2009 06:28:21 -0500 Original-Received: from [199.232.76.173] (port=52510 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ld0tA-0004Pv-MY for emacs-devel@gnu.org; Fri, 27 Feb 2009 06:28:20 -0500 Original-Received: from mtaout2.012.net.il ([84.95.2.4]:42531) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from <eliz@gnu.org>) id 1Ld0t9-0007Tp-UL for emacs-devel@gnu.org; Fri, 27 Feb 2009 06:28:20 -0500 Original-Received: from conversion-daemon.i_mtaout2.012.net.il by i_mtaout2.012.net.il (HyperSendmail v2004.12) id <0KFQ000002BSJZ00@i_mtaout2.012.net.il> for emacs-devel@gnu.org; Fri, 27 Feb 2009 13:28:56 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([77.127.167.119]) by i_mtaout2.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KFQ00DP32K6PPF0@i_mtaout2.012.net.il>; Fri, 27 Feb 2009 13:28:55 +0200 (IST) In-reply-to: <87tz6i6kug.fsf@cyd.mit.edu> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.gnu.org: Solaris 9.1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." <emacs-devel.gnu.org> List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>, <mailto:emacs-devel-request@gnu.org?subject=unsubscribe> List-Archive: <http://lists.gnu.org/pipermail/emacs-devel> List-Post: <mailto:emacs-devel@gnu.org> List-Help: <mailto:emacs-devel-request@gnu.org?subject=help> List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>, <mailto:emacs-devel-request@gnu.org?subject=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:109364 Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/109364> > From: Chong Yidong <cyd@stupidchicken.com> > Date: Wed, 25 Feb 2009 20:35:51 -0500 > > Emacs pretest 23.0.91 is now available for download via FTP, at the > following location: > > http://alpha.gnu.org/gnu/emacs/pretest/emacs-23.0.91.tar.gz > > The xdelta against the previous pretest, 23.0.90, is here: > > http://alpha.gnu.org/gnu/emacs/pretest/emacs-23.0.90-23.0.91.xdelta > > This is the second pretest for what will be the Emacs 23.1 release. > > Pretesters: please send an email to me reporting success or failure on > your build platform. This pretest compiles with --without-x and works on the following system: Linux fencepost 2.6.16.29-xen #1 SMP Wed Dec 6 07:32:36 EST 2006 x86_64 GNU/Linux However, the problem with gratuitous compilation of Lisp files, which was reported in Bug #2151, is still there. I will send a separate message as a followup to the bug report, suggesting some new ideas on how to resolve that.