Date: Tue, 27 Nov 2001 16:37:49 -0500 (EST) From: Robert Watson <rwatson@FreeBSD.org> To: Mike Barcroft <mike@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Committer's guide policy on commit message contents Message-ID: <Pine.NEB.3.96L.1011127163632.20120A-100000@fledge.watson.org> In-Reply-To: <20011127163513.A12400@espresso.q9media.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 27 Nov 2001, Mike Barcroft wrote: > From the Committers Guide: "Do not waste space in the commit messages > explaining what you did. That is what cvs diff is for. Instead, tell > us why you did it." 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? Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services 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?Pine.NEB.3.96L.1011127163632.20120A-100000>