From owner-cvs-all  Wed Aug 23  9:52:29 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 9FD1137B42C; Wed, 23 Aug 2000 09:52:21 -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 KAA07264;
	Wed, 23 Aug 2000 10:52:16 -0600 (MDT)
	(envelope-from nate@nomad.yogotech.com)
Received: (from nate@localhost)
	by nomad.yogotech.com (8.8.8/8.8.8) id KAA12190;
	Wed, 23 Aug 2000 10:51:00 -0600 (MDT)
	(envelope-from nate)
Date: Wed, 23 Aug 2000 10:51:00 -0600 (MDT)
Message-Id: <200008231651.KAA12190@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: Warner Losh <imp@village.org>
Cc: nate@yogotech.com (Nate Williams),
	Josef Karthauser <joe@pavilion.net>,
	"David O'Brien" <obrien@FreeBSD.org>,
	Jeroen Ruigrok van der Werven <asmodai@FreeBSD.org>,
	Peter Wemm <peter@netplex.com.au>, Doug Barton <DougB@gorean.org>,
	Ade Lovett <ade@FreeBSD.org>, Jonathan Lemon <jlemon@FreeBSD.org>,
	cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: Re: cvs commit: src/games/fortune/datfiles fortunes 
In-Reply-To: <200008231648.KAA02382@billy-club.village.org>
References: <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>
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

> : > The per-commit id is also going in.  Question is what kind of format
> : > if should be.  It could be an integer counter, or a YYYYMMDD-CID  (commit
> : > id) type.  Preferences?
> : 
> : The latter, unless you've figured out a way to have the counter updated
> : on a per-branch basis.  (Counters should only be incremented when a file
> : on that branch is touched, else keeping track of the 'state' of the tree
> : is too difficult.)
> 
> Actually, having a strict incremental counter is fine, even with
> branching. If I make a commit to branch X that is number 100, an then
> 20 commits happen on the main line, and than I make another commit on
> branch X (now commit number 121) branch X happens to be the same for
> numbers 100-120, but I don't see that being a big deal.

Unfortunately, it makes it difficult to know how many 'changes' have
gone on since you last updated.  Plus, you don't necessarily know
*which* change you are on when you CVSup the tree, since the counter is
not kept as part of the repository.


Nate


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