Date: Thu, 6 Feb 1997 01:25:25 -0800 (PST) From: asami@vader.cs.berkeley.edu (Satoshi Asami) To: gjennejohn@frt.dec.com Cc: current@freebsd.org Subject: Re: conditionally including <sys/param.h> Message-ID: <199702060925.BAA22067@silvia.HIP.Berkeley.EDU> In-Reply-To: <9702051033.AA17951@cssmuc.frt.dec.com> (garyj@frt.dec.com)
next in thread | previous in thread | raw e-mail | index | archive | help
* From: garyj@frt.dec.com * what I'd lioke to see in -current (aka 3.0) is __FreeBSD__=3 instead of * __FreeBSD__=2. This would make it easier to differentiate between 2.2 and I agree with this. Also, I would like to propose to have osreldate updated in a way that all 2.1*s come before all 2.2*s and they come before all 3.*s. As seen in the recent top port debacle, simply using the release year/month is bound to utter confusion. Right now we have (from the handbook): === 2.0-RELEASE: 199411 2.1-current's: 199501, 199503 2.0.5-RELEASE: 199504 2.2-current before 2.1: 199508 2.1.0-RELEASE: 199511 2.2-current before 2.1.5: 199512 2.1.5-RELEASE: 199607 2.2-current before 2.1.6: 199608 2.1.6-RELEASE: 199612 2.2-RELEASE: 199701 3.0-current as of Feb 1997: 199702 (will certainly be bumped) === Obviously everything up to 2.1.6R can't be changed, but the last two are still salvagable. Let's say we make them === 2.2-RELEASE: 199707 3.0-current as of Feb 1997: 199801 === so we have more space to squeeze in 2.1.7R and 2.2.5R and such without sacrificing the linear ordering. Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702060925.BAA22067>