From owner-cvs-all  Wed Aug 23 10:44:42 2000
Delivered-To: cvs-all@freebsd.org
Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66])
	by hub.freebsd.org (Postfix) with ESMTP
	id D30CB37B424; Wed, 23 Aug 2000 10:44:38 -0700 (PDT)
Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131])
	by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id LAA08213;
	Wed, 23 Aug 2000 11:44:34 -0600 (MDT)
	(envelope-from nate@nomad.yogotech.com)
Received: (from nate@localhost)
	by nomad.yogotech.com (8.8.8/8.8.8) id LAA13050;
	Wed, 23 Aug 2000 11:43:14 -0600 (MDT)
	(envelope-from nate)
Date: Wed, 23 Aug 2000 11:43:14 -0600 (MDT)
Message-Id: <200008231743.LAA13050@nomad.yogotech.com>
From: Nate Williams <nate@yogotech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Josef Karthauser <joe@pavilion.net>
Cc: Nate Williams <nate@yogotech.com>, Warner Losh <imp@village.org>,
	cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: Re: cvs commit: src/games/fortune/datfiles fortunes
In-Reply-To: <20000823184240.B13773@pavilion.net>
References: <200008231651.KAA12190@nomad.yogotech.com>
	<200008231604.KAA11402@nomad.yogotech.com>
	<20000814003636.A74639@pavilion.net>
	<200008140753.AAA08038@netplex.com.au>
	<20000819124824.E88550@lucifer.bart.nl>
	<20000822161835.B807@dragon.nuxi.com>
	<20000823091714.D650@pavilion.net>
	<200008231648.KAA02382@billy-club.village.org>
	<200008231704.LAA02617@billy-club.village.org>
	<200008231707.LAA12343@nomad.yogotech.com>
	<20000823184240.B13773@pavilion.net>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Reply-To: nate@yogotech.com (Nate Williams)
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > > Also, I don't see a functional difference between DATE-NUMBER and just
> > > NUMBER,  especially since it isn't in the CVS tree.  However, a GMT
> > > date down to the second as a change number id, then that would make
> > > checking out from CVS to that point possible.
> > 
> > That would be cool.  Actually, a GMT date would be adequate for me,
> > instead of using a number, since that makes things really easy from a
> > CVS point of view.  I'd actually prefer that to a number, for the
> > reasons mentioned.
> 
> If we had an incrementing number we need locking and a counter file.

Agreed.

> If we have "utime/user" we probably don't.  Utime (by which I mean
> any format with a resolution of a second) on it's own probably isn't
> sufficient without a lock and a sub increment counter (although a byte
> from /dev/urandom may work..... only joking! :)

Actually, given the updates from CVS, I think a utime counter is quite
adequate.  I don't think we're pushing multiple updates/sec at this
point.


Nate


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message