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: Moving files from lisp/gnus/ to lisp/net/? Date: Mon, 25 Oct 2004 10:02:36 +0900 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: References: <20041020105027.GA17283@fencepost> 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 1098666203 13166 80.91.229.6 (25 Oct 2004 01:03:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 25 Oct 2004 01:03:23 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 25 03:03:10 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 1CLtGQ-0007NS-00 for ; Mon, 25 Oct 2004 03:03:10 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CLtO2-0003Sg-Mt for ged-emacs-devel@m.gmane.org; Sun, 24 Oct 2004 21:11:02 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CLtNu-0003SU-KR for emacs-devel@gnu.org; Sun, 24 Oct 2004 21:10:54 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CLtNt-0003SG-Qo for emacs-devel@gnu.org; Sun, 24 Oct 2004 21:10:54 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CLtNt-0003SD-Lt for emacs-devel@gnu.org; Sun, 24 Oct 2004 21:10:53 -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 1CLtG2-0004B0-81; Sun, 24 Oct 2004 21:02:46 -0400 Original-Received: from mailgate3.nec.co.jp (mailgate99.nec.co.jp [10.7.69.186]) by tyo202.gate.nec.co.jp (8.11.7/3.7W01080315) with ESMTP id i9P12fn13135; Mon, 25 Oct 2004 10:02:41 +0900 (JST) Original-Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id i9P12fR03101; Mon, 25 Oct 2004 10:02:41 +0900 (JST) Original-Received: from edtmg02.lsi.nec.co.jp ([10.26.16.202]) by mailsv4.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with ESMTP id i9P12dN03517; Mon, 25 Oct 2004 10:02:39 +0900 (JST) Original-Received: from mcsss2.ucom.lsi.nec.co.jp (localhost [127.0.0.1]) by edtmg02.lsi.nec.co.jp (8.12.10/8.12.10) with ESMTP id i9P12cn2029269; Mon, 25 Oct 2004 10:02:39 +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 i9P12cwt013851; Mon, 25 Oct 2004 10:02:38 +0900 (JST) Original-Received: by mctpc71 (Postfix, from userid 31295) id 598D5429; Mon, 25 Oct 2004 10:02:37 +0900 (JST) Original-To: emacs-devel@gnu.org System-Type: i686-pc-linux-gnu Blat: Foop In-Reply-To: (Lars Magne Ingebrigtsen's message of "Sat, 23 Oct 2004 09:48:12 +0200") Original-Lines: 41 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:28872 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:28872 Lars Magne Ingebrigtsen writes: > Hm. That would work. But perhaps the best solution is to not move > any files after all. :-) No, I think the files should be moved; the whole "but what about the history?" issue is IMHO, vastly overrated -- it's a minor bump in the road (if even that) that will make future operations smoother. Remember, the _info is still there_, just slightly more annoying to get at. In my experience, looking at history is (1) not all that frequent an event, and (2) almost always involves the last few file revisions; point (2) is important because it means for commonly changed files, the bump caused by file moving will cease to be an issue after a short while (and for _un_-commonly changed files, well, they're not being changed very often, so aren't something to worry about very much). Moving the files will simplify coordination with Emacs, and not just with regard to the source-code "syncing" process: more importantly, it will clearly communicate to Gnus developers the status of a file they're working on, and make its relationship with Emacs obvious. Morever I think Gnus is large enough that some more directory structure is a good thing even without Emacs coordination to worry about. > If we had a specific and set mapping maintained in a file that said > where each file is supposed to go, then perhaps Miles would be able > to sort things out automatically? Maintaining a mapping between emacs locations and Gnus locations is not generally a problem for me -- arch applies changesets according to file-id, not name. There is a slight benefit to having similar directory structures when files are added/removed, as I probably don't have to worry about adjusting the names in that case. However this is a relatively rare event. -Miles -- We are all lying in the gutter, but some of us are looking at the stars. -Oscar Wilde