From owner-cvs-all Tue Nov 27 13:53:36 2001 Delivered-To: cvs-all@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 671B037B416; Tue, 27 Nov 2001 13:45:35 -0800 (PST) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 168q4G-000N5O-00; Tue, 27 Nov 2001 23:47:04 +0200 From: Sheldon Hearn To: Robert Watson Cc: Mike Barcroft , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: Committer's guide policy on commit message contents In-reply-to: Your message of "Tue, 27 Nov 2001 16:37:49 EST." Date: Tue, 27 Nov 2001 23:47:04 +0200 Message-ID: <88745.1006897624@axl.seasidesoftware.co.za> 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 Tue, 27 Nov 2001 16:37:49 EST, Robert Watson wrote: | Ignoring, for a moment, any context -- I think this is actually not a good | policy. In the event that there are complex or large changes being made, | a brief summary of the changes, along with the rationale, is appropriate | in the commit message. At least, that's my feeling :-). Is this | something that would be worth changing? The only thing that would make me disagree with you would be a persistent, well-indexed and easily driven web site on which minipapers explaining complex changes could be published and then referenced from within commit messages. And then only for large (50+ line) commit messages. We don't have that now, so I'm with you until that changes. ;-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message