From owner-cvs-all@FreeBSD.ORG Wed Feb 1 18:12:17 2006 Return-Path: X-Original-To: cvs-all@FreeBSD.org Delivered-To: cvs-all@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E3B316A420; Wed, 1 Feb 2006 18:12:17 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AB9B43D48; Wed, 1 Feb 2006 18:12:17 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k11IB3m7056333; Wed, 1 Feb 2006 11:11:03 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 01 Feb 2006 11:11:03 -0700 (MST) Message-Id: <20060201.111103.71145408.imp@bsdimp.com> To: peterjeremy@optushome.com.au From: Warner Losh 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> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 01 Feb 2006 11:11:03 -0700 (MST) 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 X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2006 18:12:17 -0000 From: Peter Jeremy 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