From owner-cvs-all@FreeBSD.ORG Wed May 28 19:17:36 2008 Return-Path: Delivered-To: cvs-all@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C2F91065670; Wed, 28 May 2008 19:17:36 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from zim.MIT.EDU (ZIM.MIT.EDU [18.95.3.101]) by mx1.freebsd.org (Postfix) with ESMTP id 846358FC18; Wed, 28 May 2008 19:17:35 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from zim.MIT.EDU (localhost [127.0.0.1]) by zim.MIT.EDU (8.14.2/8.14.2) with ESMTP id m4SJI7Ag008206; Wed, 28 May 2008 15:18:07 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by zim.MIT.EDU (8.14.2/8.14.2/Submit) id m4SJI76d008205; Wed, 28 May 2008 15:18:07 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Date: Wed, 28 May 2008 15:18:07 -0400 From: David Schultz To: Daniel Eischen Message-ID: <20080528191807.GA8156@zim.MIT.EDU> Mail-Followup-To: Daniel Eischen , d@delphij.net, Maxim Sobolev , Xin LI , src-committers@FreeBSD.ORG, cvs-src@FreeBSD.ORG, cvs-all@FreeBSD.ORG, re@FreeBSD.ORG References: <200805272004.m4RK4SZt029194@repoman.freebsd.org> <483C7FF2.6000607@FreeBSD.org> <483C977F.20105@delphij.net> <20080528060333.GA4699@zim.MIT.EDU> <20080528184143.GA7624@zim.MIT.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: Maxim Sobolev , src-committers@FreeBSD.ORG, d@delphij.net, cvs-src@FreeBSD.ORG, cvs-all@FreeBSD.ORG, Xin LI , re@FreeBSD.ORG Subject: Re: cvs commit: src/include string.h src/lib/libc/string Makefile.inc memchr.3 memrchr.c src/sys/sys param.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, 28 May 2008 19:17:36 -0000 On Wed, May 28, 2008, Daniel Eischen wrote: > On Wed, 28 May 2008, David Schultz wrote: > > >On Wed, May 28, 2008, Daniel Eischen wrote: > >>No, all new symbols in 8-current go into FBSD_1.1, not 1.2. The > >>only time we go to 1.2 is when 8.x branches to 9.0. If for some > >>reason memrchr() were to change its ABI, then we would go to 1.1.1 > >>in -current for the ABI change and any subsequent new symbols, and > >>the MFC to 7.x would also be 1.1.1. > >> > >>It is ok for a FBSD_1.1 in -current to be a superset of FBSD_1.1 > >>in a previous branch. In fact you can't prevent them from being > >>different unless you mandate that all new symbols get MFC'd to > >>their respective namespaces in previous branches. > > > >Perhaps I misinterpreted what you said about this last year, but I > >thought you said you didn't want symbols added to existing > >namespaces in -STABLE. In 7.X, why would it be okay to add new > >symbols to FBSD_1.1 between releases but not to FBSD_1.0? > > I think you're just off by a version. -stable didn't have > FBSD_1.1, so we just _did_ add memrchr() to a _new_ namespace > in -stable. Yes, yes, that's fine, that's what I said. But you also said it's fine to add things to FBSD_1.1 in 7.X, which I think is different from what you told me last year... In practice, this means that if a binary uses FBSD_1.0 and FBSD_1.1 symbols, the only thing you can say with confidence is that it will run in 8.0-RELEASE. That's fine with me; I'd just like to make sure I understand what you do and don't intend to guarantee.