Date: Mon, 6 Oct 1997 08:08:48 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com> To: imp@village.org (Warner Losh) Cc: chad@dcfinc.com, dg@root.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu, freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP vs. SNAPS Message-ID: <199710061508.IAA00318@GndRsh.aac.dev.com> In-Reply-To: <199710022335.RAA06331@harmony.village.org> from Warner Losh at "Oct 2, 97 05:35:52 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> In message <199710022331.QAA29397@freebie.dcfinc.com> "Chad R. Larson" writes: > : In other words, say I get my new, hot 2.2.5-RELEASE CD-ROMs from Walnut > : Creek via my subscription. I build a brand new box and load it from the > : CD. Then I CVSup against 2.2-STABLE to pick up any last minute bug > : fixes. What should the release identifier be now? Whatever it is, it > : should be different than before the CVSup. And it should be something > : that can be easily determined from within a script, for autoconfigures > : and the like. > > Unless I'm missing something, that's what I'm proposing. uname -r > should return 2.2.5-STABLE in this scenario. This is a good > compromise between being too precise (heisenberg would have something > to say about the CVS tree, if Terry doesn't beat him to it) and too > vauge (the current status quo). And it did this, when I was still pretty active in this stuff: Script started on Mon Oct 6 08:08:08 1997 GndRsh# uname -r 2.1.5-STABLE GndRsh# exit Script done on Mon Oct 6 08:08:11 1997 -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710061508.IAA00318>