From owner-freebsd-threads@FreeBSD.ORG  Mon Feb  4 17:10:36 2008
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: threads@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E50BC16A46B;
	Mon,  4 Feb 2008 17:10:34 +0000 (UTC)
	(envelope-from deischen@freebsd.org)
Received: from mail.netplex.net (mail.netplex.net [204.213.176.10])
	by mx1.freebsd.org (Postfix) with ESMTP id 9E90213C455;
	Mon,  4 Feb 2008 17:10:34 +0000 (UTC)
	(envelope-from deischen@freebsd.org)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
	by mail.netplex.net (8.14.2/8.14.2/NETPLEX) with ESMTP id
	m14HASWc003786; Mon, 4 Feb 2008 12:10:28 -0500 (EST)
X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net)
X-Greylist: Message whitelisted by DRAC access database, not delayed by
	milter-greylist-4.0 (mail.netplex.net [204.213.176.10]);
	Mon, 04 Feb 2008 12:10:29 -0500 (EST)
Date: Mon, 4 Feb 2008 12:10:29 -0500 (EST)
From: Daniel Eischen <deischen@freebsd.org>
X-X-Sender: eischen@sea.ntplx.net
To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
In-Reply-To: <86r6fsd55s.fsf@ds4.des.no>
Message-ID: <Pine.GSO.4.64.0802041206270.13899@sea.ntplx.net>
References: <861w7um5o5.fsf@ds4.des.no>
	<e7db6d980802030759x6db9bf1dq8992542bd8d2e017@mail.gmail.com>
	<20080203162918.GK57756@deviant.kiev.zoral.com.ua>
	<20080203121112.426a8c25@kan.dnsalias.net>
	<86zlugeqaz.fsf@ds4.des.no>
	<Pine.GSO.4.64.0802041146260.13899@sea.ntplx.net>
	<86r6fsd55s.fsf@ds4.des.no>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED;
	BOUNDARY="-559023410-824023566-1202145029=:13899"
Cc: threads@freebsd.org, Peter Wemm <peter@wemm.org>, current@freebsd.org
Subject: Re: Symbol versioning errors in libthr
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Daniel Eischen <deischen@freebsd.org>
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>, 
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Feb 2008 17:10:37 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---559023410-824023566-1202145029=:13899
Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Mon, 4 Feb 2008, Dag-Erling Sm=C3=B8rgrav wrote:

> Daniel Eischen <deischen@freebsd.org> writes:
>> I question the bumping of FBSDprivate to 1.1.  FBSDprivate is special,
>> it is only for use in our base system, and our supported method of
>> updating our system is buildworkd/buildkernel - so any changes to
>> FBSDprivate should be unnoticed.
>
> A whole lot of assumptions there.  Bumping FBSDprivate costs nothing and
> might save our a***s down the road if one of those assumptions turn out
> to be false.

If there is a need for it, it can be bumped.  There is no need as
yet.  The only need for bumping private is for an ABI change, and
if that ABI change cannot be picked up in a buildworld.  This is
what FBSDprivate was designed for.

> (unless you can show that it's actually harmful in some way?)

Please do not bump private, it was never meant to be bumped like
this.

--=20
DE
---559023410-824023566-1202145029=:13899--