From owner-cvs-all Wed Aug 29 5:39: 6 2001 Delivered-To: cvs-all@freebsd.org Received: from elm.phenome.org (elm.phenome.org [194.153.169.3]) by hub.freebsd.org (Postfix) with ESMTP id 9CE7737B401; Wed, 29 Aug 2001 05:39:01 -0700 (PDT) (envelope-from joshua@roughtrade.net) Received: from localhost (joshua@localhost [127.0.0.1]) by localhost (8.12.0.Beta19/8.12.0.Beta19/Debian 8.12.0.Beta19) with ESMTP id f7TCcavR010119; Wed, 29 Aug 2001 13:38:36 +0100 Date: Wed, 29 Aug 2001 13:38:36 +0100 (BST) From: Joshua Goodall X-X-Sender: To: Brian Somers Cc: Giorgos Keramidas , , , Subject: Re: cvs commit: src/etc/defaults rc.conf src/etc/mtree BSD.var.dist src/etc/namedb named.conf In-Reply-To: <200108291125.f7TBPLf74224@hak.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 29 Aug 2001, Brian Somers wrote: > A not-updated configuration file should never become invalid after a > -stable update, not unless there are exceptional circumstances and > it's documented in UPDATING. ... and the requirement for mergemaster support, to update those configuration files & file structures. Any admin who updates -stable without mergemaster should be skinned alive and has probably already been burnt on more than one occasion. If we didn't have that facility, we'd have a lot more legacy configuration baggage to carry around, and -stable would become -stagnant. With my admin hat on, I expect MFC'd new features, not just bugfixes and security patches in -stable. J To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message