From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: Gnus update Date: Fri, 16 Jul 2004 18:08:56 +0900 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <1890.1089689203@newt.com> <2914-Tue13Jul2004070451+0300-eliz@gnu.org> <3589.1089692661@newt.com> <2914-Tue13Jul2004215551+0300-eliz@gnu.org> <861xjfkpgu.fsf@rumba.de.uu.net> <9003-Wed14Jul2004233535+0300-eliz@gnu.org> <20040714221345.GB27263@fencepost> <86acy1n92r.fsf@rumba.de.uu.net> Reply-To: Miles Bader NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1089968982 26310 80.91.224.253 (16 Jul 2004 09:09:42 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 16 Jul 2004 09:09:42 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri Jul 16 11:09:34 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BlOik-0005rc-00 for ; Fri, 16 Jul 2004 11:09:34 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BlOik-0002zP-00 for ; Fri, 16 Jul 2004 11:09:34 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BlOlG-0001P4-MX for emacs-devel@quimby.gnus.org; Fri, 16 Jul 2004 05:12:10 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BlOl5-0001Ox-Ed for emacs-devel@gnu.org; Fri, 16 Jul 2004 05:11:59 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BlOl4-0001Oe-5n for emacs-devel@gnu.org; Fri, 16 Jul 2004 05:11:58 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BlOl4-0001OU-3y for emacs-devel@gnu.org; Fri, 16 Jul 2004 05:11:58 -0400 Original-Received: from [202.32.8.202] (helo=tyo202.gate.nec.co.jp) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BlOiF-0002sG-Aq; Fri, 16 Jul 2004 05:09:03 -0400 Original-Received: from mailgate3.nec.co.jp (mailgate53.nec.co.jp [10.7.69.161] (may be forged)) by tyo202.gate.nec.co.jp (8.11.7/3.7W01080315) with ESMTP id i6G990T25334; Fri, 16 Jul 2004 18:09:00 +0900 (JST) Original-Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id i6G990S27942; Fri, 16 Jul 2004 18:09:00 +0900 (JST) Original-Received: from edtmg03.lsi.nec.co.jp ([10.26.16.203]) by mailsv5.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with ESMTP id i6G98wa00629; Fri, 16 Jul 2004 18:08:58 +0900 (JST) Original-Received: from mcsss2.ucom.lsi.nec.co.jp (localhost [127.0.0.1]) by edtmg03.lsi.nec.co.jp (8.12.10/8.12.10) with ESMTP id i6G98vnZ024174; Fri, 16 Jul 2004 18:08:57 +0900 (JST) Original-Received: from mctpc71 (mctpc71.ucom.lsi.nec.co.jp [10.30.118.121]) by mcsss2.ucom.lsi.nec.co.jp (8.12.10/8.12.8/EDcg v2.01-mc/1046780839) with ESMTP id i6G98uwt013980; Fri, 16 Jul 2004 18:08:56 +0900 (JST) Original-Received: by mctpc71 (Postfix, from userid 31295) id 8128D24; Fri, 16 Jul 2004 18:08:56 +0900 (JST) Original-To: David Kastrup System-Type: i686-pc-linux-gnu Blat: Foop In-Reply-To: (David Kastrup's message of "16 Jul 2004 10:57:12 +0200") Original-Lines: 22 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: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:25750 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:25750 David Kastrup writes: > How is this going to be managed? After all, Gnus also works for > XEmacs. If it is maintained straight in the Emacs CVS trunk, this > might affect the average stability experienced by XEmacs users. If > we have just a one-way copy of gnus within Emacs, then we probably > need to make it explicitly read-only in some manner to avoid having > fixes disappear. I think the best thing might be to have neither, but rather do two-way merging very frequently. Since most changes do actually occur in the Gnus tree, this would end up being "mostly" one-way. To make it practical, there would probably have to be some awareness on the part of emacs hackers of the situation (e.g., some care to not remove xemacs-specific code whereas my impression is that before this was done freely in the emacs branch of gnus); perhaps the relative rarity of emacs->gnus changes would make it not _that_ much an issue. -Miles -- Is it true that nothing can be known? If so how do we know this? -Woody Allen