From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: Upcoming 23.1 release Date: Tue, 21 Jul 2009 09:43:24 +0900 Message-ID: References: <87ws63cij1.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1248137030 9827 80.91.229.12 (21 Jul 2009 00:43:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 21 Jul 2009 00:43:50 +0000 (UTC) Cc: ynyaaa@ybb.ne.jp, emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jul 21 02:43:43 2009 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 1MT3SI-0005OM-MQ for ged-emacs-devel@m.gmane.org; Tue, 21 Jul 2009 02:43:42 +0200 Original-Received: from localhost ([127.0.0.1]:44943 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MT3SI-0002xR-26 for ged-emacs-devel@m.gmane.org; Mon, 20 Jul 2009 20:43:42 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MT3SC-0002xL-8Y for emacs-devel@gnu.org; Mon, 20 Jul 2009 20:43:36 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MT3S7-0002x5-C8 for emacs-devel@gnu.org; Mon, 20 Jul 2009 20:43:35 -0400 Original-Received: from [199.232.76.173] (port=50710 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MT3S7-0002x2-6T for emacs-devel@gnu.org; Mon, 20 Jul 2009 20:43:31 -0400 Original-Received: from mx1.aist.go.jp ([150.29.246.133]:46466) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MT3S6-0007VO-Dn for emacs-devel@gnu.org; Mon, 20 Jul 2009 20:43:30 -0400 Original-Received: from rqsmtp1.aist.go.jp (rqsmtp1.aist.go.jp [150.29.254.115]) by mx1.aist.go.jp with ESMTP id n6L0hPmv007952; Tue, 21 Jul 2009 09:43:25 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp1.aist.go.jp by rqsmtp1.aist.go.jp with ESMTP id n6L0hPhF010942; Tue, 21 Jul 2009 09:43:25 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp1.aist.go.jp with ESMTP id n6L0hOxs014277; Tue, 21 Jul 2009 09:43:24 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken with local (Exim 4.69) (envelope-from ) id 1MT3S0-00060p-Gk; Tue, 21 Jul 2009 09:43:24 +0900 In-Reply-To: <87ws63cij1.fsf@stupidchicken.com> (message from Chong Yidong on Mon, 20 Jul 2009 14:32:18 -0400) X-detected-operating-system: by monty-python.gnu.org: Solaris 9 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:112874 Archived-At: In article <87ws63cij1.fsf@stupidchicken.com>, Chong Yidong writes: > As mentioned earlier, the 23.1 release is currently scheduled for this > Wednesday. > There are a couple of problems which probably can't be fixed without > destabilizing the branch and significantly delaying the release. These > are (i) the rmail auto-save issue, (ii) a bug in vertical-motion > involving continued a particular combination of tab characters > (Bug#3879), and (iii) the remaining issues with the Cocoa port. I think > it's OK to leave these for 23.2. If anyone has objections to these or > other issues, now is the time to raise them. I've just got a bug report about tar-mode on Windows. Here's the translation of the report (original in Japanese) ---------------------------------------------------------------------- On Windows, when we edit a tar file in tar-mode, the file is broken. It seems that this is because default-buffer-file-coding-system is japanese-shift-jis-dos, and thus this eol-conversion takes effect on writing a tar file. ---------------------------------------------------------------------- At the moment, I'm too busy to verify that report. But, if this bug really exists, it should be fixed before the release, and I believe the fix is not that difficult. --- Kenichi Handa handa@m17n.org