Date: Fri, 14 Dec 2007 12:42:59 -0500 From: David Schultz <das@FreeBSD.ORG> To: Daniel Eischen <deischen@FreeBSD.ORG> Cc: Yar Tikhiy <yar@FreeBSD.ORG>, Alexander Kabaev <kabaev@gmail.com>, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/lib/msun Symbol.map Message-ID: <20071214174259.GA35869@VARK.MIT.EDU> In-Reply-To: <Pine.GSO.4.64.0712141118200.16719@sea.ntplx.net> References: <200712140308.lBE38Ae7061160@repoman.freebsd.org> <20071213235617.2b554b60@kan.dnsalias.net> <Pine.GSO.4.64.0712140024230.14620@sea.ntplx.net> <20071214083507.GA33635@VARK.MIT.EDU> <Pine.GSO.4.64.0712141118200.16719@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 14, 2007, Daniel Eischen wrote: > No, everytime we branch a release from -current (e.g, at 8.0, > 9.0, etc), we should increment the namespace. -current typically > stays at the same number for quite a while (1-3 years?). We > go to FBSD_1.1 now in 8-current. Check with re@ and see if > you can MFC your symbols before 7.0. If not, then move them > to FBSD_1.1 in -current. If you have to MFC symbols from > FBSD_1.1 in -current, then just add those symbols to FBSD_1.1 > in 7.x. > > Whatever happens, the symbols in release N.x must be present in > the same namespaces as release N.x+y through -current to > maintain backward compatibility. The opposite is not true, > as release N.x+y can contain a superset of symbols from > release N.x. Okay, I'll go ahead and do that. Adding a new namespace for every major release sounds reasonable; I just didn't like the idea of adding a new namespace for every MFCable change.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071214174259.GA35869>