Date: Tue, 27 Nov 2001 23:47:04 +0200 From: Sheldon Hearn <sheldonh@starjuice.net> To: Robert Watson <rwatson@FreeBSD.org> Cc: Mike Barcroft <mike@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: Committer's guide policy on commit message contents Message-ID: <88745.1006897624@axl.seasidesoftware.co.za> In-Reply-To: Your message of "Tue, 27 Nov 2001 16:37:49 EST." <Pine.NEB.3.96L.1011127163632.20120A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?88745.1006897624>