From owner-cvs-all Wed Aug 23 10: 5: 6 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 3430137B423; Wed, 23 Aug 2000 10:05:00 -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 LAA07470; Wed, 23 Aug 2000 11:04:55 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id LAA12281; Wed, 23 Aug 2000 11:03:39 -0600 (MDT) (envelope-from nate) Date: Wed, 23 Aug 2000 11:03:39 -0600 (MDT) Message-Id: <200008231703.LAA12281@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Josef Karthauser Cc: Nate Williams , Warner Losh , "David O'Brien" , Jeroen Ruigrok van der Werven , Peter Wemm , Doug Barton , Ade Lovett , Jonathan Lemon , cvs-committers@FREEBSD.ORG, cvs-all@FREEBSD.ORG Subject: Re: cvs commit: src/games/fortune/datfiles fortunes In-Reply-To: <20000823180308.C12911@pavilion.net> 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> <200008231651.KAA12190@nomad.yogotech.com> <20000823180308.C12911@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 > > > 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. > > > > It's probably easier, and less error prone, to have a single counter. > Maintaining one per branch is a pain - considering how many branches > there are, including different vendor branches. > > > 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. > > Although it should be a file in CVSROOT, and so will probably turn > up with a cvsup of the repository. Obviously not under CVS control right? You may need to talk with John Polstra about having a file that's constantly changing that is not under CVS control, to make sure CVSup will 'Do The Right Thing'. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message