Date: Thu, 20 Nov 1997 17:35:22 -0700 (MST) From: "Chad R. Larson" <chad@freebie.dcfinc.com> To: nate@mt.sri.com (Nate Williams) Cc: chad@dcfinc.com, nate@mt.sri.com, rkw@dataplex.net, brian@awfulhak.org, andrsn@andrsn.stanford.edu, freebsd-stable@freebsd.org Subject: Re: Version Resolution? Message-ID: <199711210035.RAA04407@freebie.dcfinc.com> In-Reply-To: <199711210029.RAA12133@mt.sri.com> from Nate Williams at "Nov 20, 97 05:29:43 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
>> > So, how do you do it? >> >> It would have to be a custom hack to CVS, letting it generate newvers.sh >> on the fly at each commit. Then "simple timestamps" =would= work. > > That's what Richard's changes were doing. They also dealt with the > issue of the files growing w/out bounds, and multiple branches, but they > *didn't* deal with new branches appearing, which was the only sticking > point I had with his solution. But there are (can be) seperate copies of newvers.sh in each branch? Seems it would be an administrative procedure to touch it correctly as part of creating a new branch. How often does that happen? Couple of times a year? > It's not as simple as it first appears to do right. If it were, they wouldn't pay us the big bucks. :-) > Nate -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com crl22@aol.com DCF, Inc. - 14523 North 49th Place, Scottsdale, Arizona 85254
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711210035.RAA04407>