Received: from spf3.us4.outblaze.com (spf3.us4.outblaze.com [205.158.62.25]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id iAG4nesw001274 for ; Tue, 16 Nov 2004 04:49:40 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf3.us4.outblaze.com (Postfix) with ESMTP id EEC3753E38 for ; Tue, 16 Nov 2004 04:49:38 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CTvPh-0004sb-NH for migo@homemail.com; Mon, 15 Nov 2004 23:57:57 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CTvPH-0004ry-6S for gnu-arch-users@gnu.org; Mon, 15 Nov 2004 23:57:31 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CTvPG-0004rT-7Q for gnu-arch-users@gnu.org; Mon, 15 Nov 2004 23:57:30 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CTvPG-0004rJ-3R for gnu-arch-users@gnu.org; Mon, 15 Nov 2004 23:57:30 -0500 Received: from [210.143.35.52] (helo=tyo202.gate.nec.co.jp) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CTvGB-0000f2-Ao; Mon, 15 Nov 2004 23:48:07 -0500 Received: from mailgate3.nec.co.jp (mailgate53.nec.co.jp [10.7.69.160] (may be forged)) by tyo202.gate.nec.co.jp (8.11.7/3.7W01080315) with ESMTP id iAG4lwn16260; Tue, 16 Nov 2004 13:47:58 +0900 (JST) Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id iAG4lwt25804; Tue, 16 Nov 2004 13:47:58 +0900 (JST) Received: from edsgm01.lsi.nec.co.jp ([10.50.208.11]) by mailsv3.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with ESMTP id iAG4lv906850; Tue, 16 Nov 2004 13:47:57 +0900 (JST) Received: from mcsss2.ucom.lsi.nec.co.jp (localhost [127.0.0.1]) by edsgm01.lsi.nec.co.jp (8.12.10/8.12.10) with ESMTP id iAG4ltIS019284; Tue, 16 Nov 2004 13:47:55 +0900 (JST) 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 iAG4lpwt026839; Tue, 16 Nov 2004 13:47:51 +0900 (JST) Received: by mctpc71 (Postfix, from userid 31295) id 8AA2C441; Tue, 16 Nov 2004 13:47:51 +0900 (JST) To: "Dimitrie O. Paun" References: <20041115191000.GA30577@rogers.com> <41990CD4.9050003@arbash-meinel.com> <20041115225611.GC28559@zipworld.com.au> <20041116043454.GT6137@rogers.com> From: Miles Bader System-Type: i686-pc-linux-gnu Blat: Foop Date: Tue, 16 Nov 2004 13:47:51 +0900 In-Reply-To: <20041116043454.GT6137@rogers.com> (Dimitrie O. Paun's message of "Mon, 15 Nov 2004 23:34:54 -0500") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: mlh@zipworld.com.au, gnu-arch-users@gnu.org Subject: [Gnu-arch-users] Re: Archives vs. categories vs. versions X-BeenThere: gnu-arch-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Miles Bader List-Id: a discussion list for all things arch-ish List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org Status: RO Content-Length: 1786 Lines: 33 "Dimitrie O. Paun" writes: > Why the time marking? I understand it's needed to work around > some performance issues, but in all honesty it looks like a > hack. Moreover, it's hard to automate. Why is it needed in to > begin with? AFAIK, the main reason for it is that archives are write-only, and given the rather rigid namespace structure of arch ("kinda flat"), means that the namespace could fill up with cruft -- temporary branches, etc. Whether this a real problem, I don't know. I've only been using arch for about 1.5 years, and don't personally seem to have generated all that much in the way of throw-away branches and the like (maybe it would be worse for shared archives). I suppose mirroring speed could be another issue, but I don't know much about that. My recollection is that the the whole-tree scan done by mirroring is already a slight problem for people like James who mirror many trees. In some sense regular archive changes could be a _good_ thing if it helped to wean people off the notion that archives are a fixed thing. However I think that there really need to be better tools for managing archive changes -- for instance, I've long wanted a feature that would inform users "hey this branch is old, please use the new one here ..."; this feature would also help with intra-archive version changes (see old threads for my suggested implementation, which may be obsolete given the recently proposed "version variables" mechanism). -Miles -- Suburbia: where they tear out the trees and then name streets after them. _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/