From owner-freebsd-current Mon Feb 12 17:11:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 3B49F37B4EC for ; Mon, 12 Feb 2001 17:11:36 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id CAA92305; Tue, 13 Feb 2001 02:11:28 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Peter Wemm Cc: Warner Losh , Daniel Eischen , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: Patch for FILE problems (was Re: -CURRENT is bad for me...) References: <200102130105.f1D15aU56009@mobile.wemm.org> From: Dag-Erling Smorgrav Date: 13 Feb 2001 02:11:26 +0100 In-Reply-To: Peter Wemm's message of "Mon, 12 Feb 2001 17:05:36 -0800" Message-ID: Lines: 18 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. When we've branched RELENG_5, if we need to bump libc's major in 6.0-CURRENT, we bump it to 600, then 601 etc. as many times as we want, and bump it down to 6 before 6.0-RELEASE. 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. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message