From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: gnus doesn't encode non-ascii attachment filenames Date: Tue, 14 Feb 2006 12:36:40 +0900 Message-ID: References: <87bqxbwxoq.fsf@emacsfans.org> <87irriras8.fsf@emacsfans.org> Reply-To: Miles Bader NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1139888266 9469 80.91.229.2 (14 Feb 2006 03:37:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 14 Feb 2006 03:37:46 +0000 (UTC) Cc: Zhang Wei , rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 14 04:37:42 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F8r0W-0005yb-KQ for ged-emacs-devel@m.gmane.org; Tue, 14 Feb 2006 04:37:41 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F8r0W-0005aj-64 for ged-emacs-devel@m.gmane.org; Mon, 13 Feb 2006 22:37:40 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F8qzo-0005Cr-IS for emacs-devel@gnu.org; Mon, 13 Feb 2006 22:36:56 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F8qzm-0005A2-43 for emacs-devel@gnu.org; Mon, 13 Feb 2006 22:36:55 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F8qzm-00059w-16 for emacs-devel@gnu.org; Mon, 13 Feb 2006 22:36:54 -0500 Original-Received: from [203.180.232.82] (helo=mgate02.necel.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F8r4F-0006Xc-79; Mon, 13 Feb 2006 22:41:31 -0500 Original-Received: from relay21.aps.necel.com (relay21 [10.29.19.50]) by mgate02.necel.com (8.13.1/8.13.1) with ESMTP id k1E3SNLZ009995; Tue, 14 Feb 2006 12:36:41 +0900 (JST) Original-Received: from relay21.aps.necel.com ([10.29.19.16] [10.29.19.16]) by relay21.aps.necel.com with ESMTP; Tue, 14 Feb 2006 12:36:41 +0900 Original-Received: from dhapc248.dev.necel.com ([10.114.97.235] [10.114.97.235]) by relay21.aps.necel.com with ESMTP; Tue, 14 Feb 2006 12:36:41 +0900 Original-Received: by dhapc248.dev.necel.com (Postfix, from userid 31295) id E42BC43F; Tue, 14 Feb 2006 12:36:40 +0900 (JST) Original-To: Kenichi Handa System-Type: i686-pc-linux-gnu Blat: Foop In-Reply-To: (Kenichi Handa's message of "Tue, 14 Feb 2006 11:13:00 +0900") Original-Lines: 19 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:50504 Archived-At: Kenichi Handa writes: > For Emacs 23, we can have a better/simpler fix. But, could someone > tell me the maintenance policy of Gnus codes? Should we modify codes > in cvs HEAD so that it works also with emacs-unicode-2 (perhaps with > version check here and there)? Or, should we directly modify codes in > cvs emacs-unicode-2? It seems to me better keep the code in both branches the same, if possible. Changes to Emacs 22 will be propagated to Gnus 5.10 and the Gnus development branch (No Gnus); as people may wish to use the Gnus development branch with Emacs 23, it would be a good thing to avoid changes which are only in the Emacs 23 sources. -Miles -- Next to fried food, the South has suffered most from oratory. -- Walter Hines Page