From owner-freebsd-stable Sun Nov 23 15:29:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA10579 for stable-outgoing; Sun, 23 Nov 1997 15:29:47 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA10574 for ; Sun, 23 Nov 1997 15:29:42 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id XAA26984; Sun, 23 Nov 1997 23:28:51 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id AAA17394; Mon, 24 Nov 1997 00:28:47 +0100 (MET) Date: Mon, 24 Nov 1997 00:28:47 +0100 (MET) Message-Id: <199711232328.AAA17394@bitbox.follo.net> From: Eivind Eklund To: Nate Williams CC: mike@smith.net.au, chad@dcfinc.com, rkw@dataplex.net, brian@awfulhak.org, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG In-reply-to: Nate Williams's message of Thu, 20 Nov 1997 16:21:17 -0700 Subject: Re: Version Resolution? References: <199711202218.PAA11561@mt.sri.com> <199711202300.JAA00612@word.smith.net.au> <199711202321.QAA11798@mt.sri.com> Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > It has to be done by CVS; each commit increments a counter. This means > > that simultaneous commits become impossible, as the object containing > > the counter has to be locked as part of the commit. > > This file then increases w/out bounds, which is unacceptable. Why? Seriously; I don't consider expanding files a good thing, but I actually can't see that this is a problem in this case. The CVS repository is increasing 'without bounds' already; we have much more data added each day than this. I don't see that this bloat is that serious. (I don't like the solution, but I don't see it as a fatal flaw - we can, if necessary, nuke the file w/history with regular intervals). Eivind.