From owner-freebsd-stable@FreeBSD.ORG Sun Feb 1 21:45:19 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CED116A4CE for ; Sun, 1 Feb 2004 21:45:19 -0800 (PST) Received: from ns1.itga.com.au (ns1.itga.com.au [202.53.40.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9546743D41 for ; Sun, 1 Feb 2004 21:45:15 -0800 (PST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns1.itga.com.au (8.12.9/8.12.9) with ESMTP id i125jER5073927; Mon, 2 Feb 2004 16:45:14 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (localhost [127.0.0.1]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id QAA20586; Mon, 2 Feb 2004 16:45:13 +1100 (EST) Message-Id: <200402020545.QAA20586@lightning.itga.com.au> X-Mailer: exmh version 2.4 05/15/2001 with nmh-1.0.4 From: Gregory Bond To: parv In-reply-to: Your message of Mon, 02 Feb 2004 00:29:50 -0500. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Feb 2004 16:45:13 +1100 Sender: gnb@itga.com.au cc: f-stable cc: Kris Kennaway Subject: Re: "make -C ..." causes error in net/tkabber/Makefile, line 17 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 05:45:19 -0000 >> No..4.8 is not maintained except for security fixes. > Even though man page & the binary will remain inconsistent w/ each > other? The point Kris is making is that the RELENG_4_8 branch represents a point in time in the development of 4-STABLE, and only critical security fixes are applied to that release. If the make document was wrong at the point in time when 4.8-RELEASE was tagged, then it will be wrong for that release for ever (unless you can convince the security officer that the doc bug is a critical security fix.....) If you think you need these sort of evolutionary improvements, then perhaps you should consider running a -STABLE version rather than a -RELEASE version. The _whole point_ of -RELEASE versions is that they don't change like this! Patches to fix 4-STABLE will be gladly accepted (if this hasn't already been fixed, which I suspect it has), but that won't change the fact that 4.8-RELEASE was wrong when it was released, and all the RELENG_4_8 versions for the rest of forever will still be wrong.