From owner-cvs-all@FreeBSD.ORG Wed May 28 17:54:41 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 722731065680 for ; Wed, 28 May 2008 17:54:41 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.234]) by mx1.freebsd.org (Postfix) with ESMTP id 446458FC47 for ; Wed, 28 May 2008 17:54:41 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: by wx-out-0506.google.com with SMTP id h27so2323470wxd.7 for ; Wed, 28 May 2008 10:54:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type; bh=G1mvxHS9aTIcHK0kLBcLjKj27Xnw2YX0V8aL5gnql6g=; b=bUONYgMwAerIkKx4gx0yx3G1ceCj1UBe74nd77kRt88STYaC9aXFUkTp2K2/+H2NdAL6fFYK8umtC9+vW6eymXftGSiw9X40At538/Ln1lQApoc12pxCGTZWXhDutnmqjbn8gqPezq72xOMUeDMZ8RLZ3QlUAAZ3fPify5bngn0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type; b=s24ycuCI9B/sAauRH+nQNUQIy3/Et1qtwEgstRBxgUMwXJQJt3jz7JMDUvdmUXEUHsnZ8zojNNaUuwHZJT1l+s32X9QJJuXoJENaFk0GcE87mEgt3mbCksjkOrgFRw/IDWVunh27FOLTfhaFw+zmUwiMynJbKTyKBw4fITNmQpk= Received: by 10.90.31.8 with SMTP id e8mr3866582age.22.1211997280307; Wed, 28 May 2008 10:54:40 -0700 (PDT) Received: from kan.dnsalias.net ( [24.218.183.247]) by mx.google.com with ESMTPS id 8sm7316632agd.21.2008.05.28.10.54.37 (version=SSLv3 cipher=RC4-MD5); Wed, 28 May 2008 10:54:38 -0700 (PDT) Date: Wed, 28 May 2008 13:54:32 -0400 From: Alexander Kabaev To: Daniel Eischen Message-ID: <20080528135432.363f363d@kan.dnsalias.net> In-Reply-To: References: <200805272004.m4RK4SZt029194@repoman.freebsd.org> <20080528091745.465f37b4@kan.dnsalias.net> X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.9; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/hSmzVtW.FXXWNcn5XmP0a.z"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: cvs-src@freebsd.org, src-committers@freebsd.org, Xin LI , cvs-all@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 17:54:41 -0000 --Sig_/hSmzVtW.FXXWNcn5XmP0a.z Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 28 May 2008 11:39:21 -0400 (EDT) Daniel Eischen wrote: > Interesting, as long as "a" =3D ".1", so that you have FBSD_1.0.1 as > the side version. >=20 > See my prior email - I thought we agreed that we just MFC the version > (in this case, FBSD_1.1) from -current. If you introduce a new > version, a binary built on 7.x may not run on -current from before > the side version was added. For instance, if we were to add > memfoo() in -current now, then we release 8.0 with memfoo@@FBSD_1.1, > then after the release we MFC memfoo() to RELENG_7 in the way > you describe, then anything built in RELENG_7 using memfoo() will > not work in 8.0 release (because 8.0 didn't have the side version > memfoo@@FBSD_1.0a/1.0.1). >=20 > Typically before a release there are a flurry of MFCs, so you can > have a few months or more elapse before the addition of new or > ABI-changed symbols. If we just use the same version as -current, > then things will just work, at least from when the symbol was > changed/added in -current. There are number of corners we can cut if we agree that being sloppy is not a problem. Then why did we bother with symbol versions in the first place? =20 > But regardless, I think this means that once we release 8.0, we > cannot MFC any new or changed symbols (from 8.0+) back to > 7.x. If someone upgrades from 7.x to 8.0, then 8.0 has to > have all the symbols that 7.x will have or else binary > compatibility will be broken. > That is why introducing new symbols in back-releases is not such a hot idea. Release X that was released after release Y cannot really be expected to be able to execute Y's binaries with 100% certainty, as that depends on guessing the future right at X ship time. --=20 Alexander Kabaev --Sig_/hSmzVtW.FXXWNcn5XmP0a.z Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFIPZxYQ6z1jMm+XZYRAtt3AJ4zPPYKVxpyUCI4NS5ovJ+6Qk0ltwCfT8aE vFRe1nqG3VFea55T92nyBCI= =Qdk5 -----END PGP SIGNATURE----- --Sig_/hSmzVtW.FXXWNcn5XmP0a.z--