Date: Tue, 27 Nov 2001 15:26:51 -0700 From: Warner Losh <imp@harmony.village.org> 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: <200111272226.fARMQpM17164@harmony.village.org> In-Reply-To: Your message of "Tue, 27 Nov 2001 16:37:49 EST." <Pine.NEB.3.96L.1011127163632.20120A-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1011127163632.20120A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.NEB.3.96L.1011127163632.20120A-100000@fledge.watson.org> Robert Watson writes: : 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? Yes. Because that's what most commit messages are anyway. Of course, I'm in the "beat the dead horse" camp of commit messages :-) Warner 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?200111272226.fARMQpM17164>