From owner-freebsd-current Mon Feb 12 17:26:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 1597737B491 for ; Mon, 12 Feb 2001 17:26:10 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1D1Q6W33680; Mon, 12 Feb 2001 18:26:07 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102130126.f1D1Q6W33680@harmony.village.org> To: Dag-Erling Smorgrav Subject: Re: Patch for FILE problems (was Re: -CURRENT is bad for me...) Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "13 Feb 2001 02:11:26 +0100." References: <200102130105.f1D15aU56009@mobile.wemm.org> Date: Mon, 12 Feb 2001 18:26:06 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Dag-Erling Smorgrav writes: : Peter Wemm writes: : > http://people.freebsd.org/~peter/stdio.diff3 : : Except that we bump to 500 instead of 6, and back to 5 before : -RELEASE. I don't think this will work. It is hard to downgrade a major number for libc.so. At least it used to be. : People tracking -CURRENT will end up with a handful of different libc : versions, but they'll avoid the pains we're going through now, and : people upgrading from RELENG_N to RELENG_N+1 will never see a libc : major version increase of more than 1. I don't see why we need only an increment of 1. What does this buy us other than a minor warm fuzzy. OpenBSD bumps libc bunchs of times per release cycle (they are up to libc.so.24 if my sources are current). I've not seen it cause problems there. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message