From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.devel Subject: Re: Moving files from lisp/gnus/ to lisp/net/? Date: Sun, 24 Oct 2004 14:59:28 +0200 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1098622879 16653 80.91.229.6 (24 Oct 2004 13:01:19 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 24 Oct 2004 13:01:19 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 24 15:01:14 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CLhzl-0007AS-00 for ; Sun, 24 Oct 2004 15:01:13 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CLi7M-00023i-Ow for ged-emacs-devel@m.gmane.org; Sun, 24 Oct 2004 09:09:04 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CLi6s-0001te-6z for emacs-devel@gnu.org; Sun, 24 Oct 2004 09:08:34 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CLi6q-0001sz-Oz for emacs-devel@gnu.org; Sun, 24 Oct 2004 09:08:33 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CLi6q-0001sw-M1 for emacs-devel@gnu.org; Sun, 24 Oct 2004 09:08:32 -0400 Original-Received: from [80.91.229.2] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CLhyS-0007j7-DL for emacs-devel@gnu.org; Sun, 24 Oct 2004 08:59:52 -0400 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CLhyR-0008Ew-00 for ; Sun, 24 Oct 2004 14:59:51 +0200 Original-Received: from c494102a.s-bi.bostream.se ([217.215.27.65]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 24 Oct 2004 14:59:51 +0200 Original-Received: from jas by c494102a.s-bi.bostream.se with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 24 Oct 2004 14:59:51 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-To: emacs-devel@gnu.org Original-Lines: 34 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: c494102a.s-bi.bostream.se Mail-Copies-To: nobody User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux) Cancel-Lock: sha1:tHmr068VoLj7CTc6unmFD0TJHDE= 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+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:28829 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:28829 Richard Stallman writes: > People seem to fear using some files in gnus/ because they think the > files might end up loading all of Gnus. I believe moving some of the > self contained files in Gnus elsewhere would be good. This would make > it clear that they aren't an intrinsic part of Gnus. Not only would > it make it clear for elisp programmers, it would make it clear for us > working on Gnus. I.e., to make sure we don't use Gnus functions in > some of the files. I just modified pop3.el to revert one such > example. It would be bad if many standalone files ended up loading > Gnus out of pure laziness. > > I agree completely. > > It makes a big difference for Emacs maintenance whether a file is part > of Gnus or not. If it is part of Gnus, it is maintained by the Gnus > developers, so they might expect to be able to change it without > looking at how the rest of Emacs uses it. My impression is that Gnus developers do not need to be able to do this now, with the new Emacs CVS and emacs-devel list. And by synchronizing the files better, it would be possible to avoid accidental changes. If anything, moving the files would make it more likely that changes are reviewed by Emacs developers, which could avoid some problems in the future. > We need to consider them one by one, so please don't raise > them as a big group. Please propose one file or a few related > files at a time, and we will think of them. > > Right now let's consider only those that there is a specific reason > to move right now. OK, I'll think about each file individually.