Date: Tue, 20 Jun 1995 05:18:41 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: bde@zeta.org.au (Bruce Evans) Cc: asami@cs.berkeley.edu, bde@zeta.org.au, bugs@freebsd.org Subject: Re: bogus release version string Message-ID: <199506201218.FAA02858@gndrsh.aac.dev.com> In-Reply-To: <199506201052.UAA06090@godzilla.zeta.org.au> from "Bruce Evans" at Jun 20, 95 08:52:28 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > * Release: FreeBSD 2.0-BUILT-19950603 i386 > > * > > * 1. This provides very little information about the version - it might be > > * for plain 2.0 built late or for 2.2 built early. > > >I agree. Is there some way to let cvs generate an $Id$-like string > >that has the checkout time, not the checkin time? Then we can put it > >in one of the header files and pull it into the kernel, and this will > >give us a reasonable approximation assuming the whole source is > >checked out at once (certainly true for sup from freefall or ctm). > > `cvs co ...; date >some-header.h' :-) > > I'd prefer for `cvs commit' to print the date step commit the changed > header (not recursively, and without doubly the number of commits). cvs co occured once for /usr/src on freefall since the 2.0 tree, it has never been checked out again. some-header.h is not how the version string gets built, it is needed by /sys/conf/newvers.sh. This would not handle the 3 way branch we now have in cvs. We need to think this throught carefully and come up with somethings that works well, but does not require excessive version reving of a commited file. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506201218.FAA02858>