From owner-freebsd-stable Thu Nov 20 15:08:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17060 for stable-outgoing; Thu, 20 Nov 1997 15:08:01 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from word.smith.net.au (s204m101.whistle.com [207.76.204.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA17016 for ; Thu, 20 Nov 1997 15:07:51 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id JAA00612; Fri, 21 Nov 1997 09:30:05 +1030 (CST) Message-Id: <199711202300.JAA00612@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Nate Williams cc: chad@dcfinc.com, rkw@dataplex.net, brian@awfulhak.org, andrsn@andrsn.stanford.edu, freebsd-stable@freebsd.org Subject: Re: Version Resolution? In-reply-to: Your message of "Thu, 20 Nov 1997 15:18:00 PDT." <199711202218.PAA11561@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Nov 1997 09:30:04 +1030 From: Mike Smith Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Where is this 'counter' stored? It's got to be in one place so that all > of the different distribution mechanisms get the same information if > they grab the same file (CTM/CVS/CVSup). If not in one place, then all > of the distribution mechanism must generate the *EXACT* same information > given the *EXACT* same information, and given that the propogation > delays of the sources throughout the world, then simple timestamps won't > work. > > So, how do you do it? 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. TBH, I don't see this as a major problem, other than that it requires (yet )a(nother) hack to CVS. mike