From owner-freebsd-stable Wed Apr 11 13:23:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from seaholm.caamora.com.au (seaholm.caamora.com.au [203.7.226.5]) by hub.freebsd.org (Postfix) with ESMTP id 1A12237B423 for ; Wed, 11 Apr 2001 13:23:50 -0700 (PDT) (envelope-from jon@seaholm.caamora.com.au) Received: (from jon@localhost) by seaholm.caamora.com.au (8.11.1/8.11.1) id f3BKLHn09841; Thu, 12 Apr 2001 06:21:17 +1000 (EST) Message-ID: <20010412062117.11022@caamora.com.au> Date: Thu, 12 Apr 2001 06:21:17 +1000 From: jonathan michaels To: Oliver Fromme Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Releases References: <20010412052718.44835@caamora.com.au> <200104111948.VAA85126@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <200104111948.VAA85126@lurza.secnetix.de>; from Oliver Fromme on Wed, Apr 11, 2001 at 09:48:57PM +0200 Organisation: Caamora, PO Box 144, Rosebery NSW 1445 Australia Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 11, 2001 at 09:48:57PM +0200, Oliver Fromme wrote: > jonathan michaels wrote: > > On Wed, Apr 11, 2001 at 03:45:41PM +0200, Oliver Fromme wrote: > > > Maybe it would reduce confusion somewhat if people would > > > just stop saying ``4.1-stable'' etc. Those simply do not > > > exist. > > > > > > I would also vote for ``uname -r'' saying ``4-STABLE'' and > > > appending the date (similar to the snapshot naming), like > > > ``4-STABLE-20010509''. This is much more useful than > > > ``4.3-STABLE'', IMO. > > > > actually, given teh granularity of teh cvs system it might be > > worthwhile to add hh:mm .. > > That would be rather difficult. > > As far as I know, there is no automatic mechanism to store > the current date and time somewhere upon a cvs checkout or > update. i wasn't sure, i am sort of fiddling with setting up some sort of source code management system (html, freebsd system sources, tcp/ip network maintenance et al) and i'm starting to get a handle on how cvs/rcs/perforce sort of work. > Anyway, just the day should be sufficient in most cases. > Think of someone posting a well-known problem to -questions > or -stable, and giving his uname output which says, for > example, ``4-STABLE-20010509''. Now we can tell him to > upgrade because it was fixed on 2001-05-20 or whatever. yup, this is what i thought would be the best and given that i couldn't see how to get the granularity required to extract teh exactly required version and given that clocks are out and given that .. a whole lot of other things i endup with (as you rightly pointed out) settling on the date of the day of teh er, um whatever that part of teh 4-stable contium would be called. > If he just said ``4.3-STABLE'', it wouldn't help much. yes, this has always been my problem since i started with freebsd back at 2.0.5-release, i could never reconcile who cvs and its mechanisms for getting and making on call 'images' so to speak of either a file, a subsystem or even teh whole of freebsd at a given point in time (usually a given day, being identified by its date). > Storing the date (without time of day) in that string would > require some cron script somewhere (probably on the master > CVS server) that updates the newvers.sh file daily. This > might sound like a gross hack, but so far I haven't seen a > better idea. "gross hack", not advocating, most people have enough on thier plates already, i can see that getting what one needs from cvs for say releng_4 for say march 23rd 2001 ... then we all can call it freebsd 4-stable-23042001. instead of freebsd 4.?-stable as of sometime early this year and teh other time frame hack normally used. > > on second thoughts your sugestion is teh > > sanest i've seen and personally wonder why it wasn't done like this > > fron teh begining. > > Probably because of the gross hack that I described above. > :-) maybe for teh hours:minutes part but for teh stable-23042001 that (from what i've managed to gather so far, ok) should be ok. just a bit of a discription reorganising because it is muchly what we are using right now, ummm i think. > But maybe someone else has a better idea how to achieve > that. given the tools we use, i think this sounds like teh most likely cource of action to take (from my perspective) but, ok, your probably right. with regards and thanks jonathan -- ================================================================ Jonathan Michaels http://www.caamora.com.au PO Box 144, Rosebery, NSW 1445 suffering construction anxiety ============================================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message