From owner-cvs-all@FreeBSD.ORG Fri Mar 12 14:41:28 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FFAF16A4CE; Fri, 12 Mar 2004 14:41:28 -0800 (PST) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5979243D31; Fri, 12 Mar 2004 14:41:28 -0800 (PST) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id F0C4614729; Fri, 12 Mar 2004 16:41:27 -0600 (CST) Date: Fri, 12 Mar 2004 16:41:27 -0600 (CST) From: Mark Linimon X-X-Sender: linimon@pancho To: Maxime Henrion In-Reply-To: <20040312223322.GF35475@elvis.mu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: Ruslan Ermilov cc: cvs-all@FreeBSD.org cc: Kris Kennaway Subject: Re: cvs commit: src/sys/kern kern_exec.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Mar 2004 22:41:28 -0000 > I believe that what Ruslan wanted to say is that since software that > will break after this commit are already broken, we can just patch the > application via the port and have it working whatever version of FreeBSD > you're running. There is also the issue of using the FreeBSD version bump as a "marker", so that when FAQs start arriving about why "something has changed", you can point the questioner to the version bump instead of "oh, there was some change to something in the kernel somewhere around that time". Now, obviously, there's no point in bumping the revision every time someone commits a file -- but in this case, where one might potentially suspect "unintended consequences", I'd rather see the project err on the side of having too many bumps rather than too few. IMHO, YMMV, etc. mcl