Date: Wed, 01 Feb 2006 11:11:03 -0700 (MST) From: Warner Losh <imp@bsdimp.com> To: peterjeremy@optushome.com.au Cc: cvs-src@FreeBSD.org, stefanf@FreeBSD.org, cvs-all@FreeBSD.org, src-committers@FreeBSD.org, kris@obsecurity.org Subject: Re: cvs commit: src/include nl_types.h Message-ID: <20060201.111103.71145408.imp@bsdimp.com> In-Reply-To: <20060201180635.GH824@turion.vk2pj.dyndns.org> References: <20060201150021.GA26651@xor.obsecurity.org> <20060201.085800.04709267.imp@bsdimp.com> <20060201180635.GH824@turion.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Peter Jeremy <peterjeremy@optushome.com.au> Subject: Re: cvs commit: src/include nl_types.h Date: Thu, 2 Feb 2006 05:06:35 +1100 > On Wed, 2006-Feb-01 08:58:00 -0700, M. Warner Losh wrote: > >Before the commit, this was true. Now you can't update to -current > >from RELENG_5. > > I didn't think this was ever guaranteed. AFAIK, the Project has > always stated that you should upgrade to the latest point on any > branch in order to be able to upgrade to the next branch. (Though > /usr/src/UPDATING does not actually state that you can only jump from > one major to the next). > > Otherwise, I'll complain that I can't get to -current from RELENG_2_2 :-) You are correct. In the past, core has allowed people to make this work, but hasn't required people to keep it working (except to the extent that core asked people to not gratuitously remove actively maintained compat code for the upgrade case). Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060201.111103.71145408.imp>