From owner-freebsd-stable Wed Apr 11 12:49: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 94A1037B423 for ; Wed, 11 Apr 2001 12:48:58 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id VAA85126; Wed, 11 Apr 2001 21:48:57 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Wed, 11 Apr 2001 21:48:57 +0200 (CEST) Message-Id: <200104111948.VAA85126@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: Releases In-Reply-To: <20010412052718.44835@caamora.com.au> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. 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. If he just said ``4.3-STABLE'', it wouldn't help much. 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. > 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. :-) But maybe someone else has a better idea how to achieve that. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message