Date: Thu, 20 Nov 1997 18:01:22 -0700 From: Nate Williams <nate@mt.sri.com> To: Brian Somers <brian@awfulhak.org> Cc: Nate Williams <nate@mt.sri.com>, Annelise Anderson <andrsn@andrsn.stanford.edu>, Richard Wackerbarth <rkw@dataplex.net>, freebsd-stable@freebsd.org Subject: Re: Version Resolution? Message-ID: <199711210101.SAA12324@mt.sri.com> In-Reply-To: <199711200426.EAA16474@awfulhak.demon.co.uk> References: <199711200146.SAA08213@mt.sri.com> <199711200426.EAA16474@awfulhak.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > The only way to get a reasonably useful date here would be to have an > > > automatic cvs posting on freefall every day to (say) sys/codedate.h: > > > > Yep, you've got it. However, this fails for people who get stuff via > > CVSup, which gets files directly out of the repository, and this file > > doesn't live in the Repository. > > But it would live in the repository. We create an original, then put > a cron job on freefall that does the "cvs co"/"cvs commit". The > ``codedate'' is actually part of the code. *ARGH* Does no-one listen? If we keep 'updating' a file in the CVS repository (be it every commit, or once/day, or whatever), then that file will grow w/out bounds, and eventually kill the jkh-AI program when it fills the disk, and our favorite entity will cease to exist. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711210101.SAA12324>