Date: Mon, 30 Oct 2006 10:56:31 -0800 From: Doug Barton <dougb@FreeBSD.org> To: "Ion-Mihai \"IOnut\" Tetcu" <itetcu@FreeBSD.org> Cc: Andrew Pantyukhin <infofarmer@FreeBSD.org>, freebsd-ports@freebsd.org, Christopher Boumenot <boumenot@gmail.com> Subject: Re: port_history - track port commit message comments Message-ID: <45464ADF.7040201@FreeBSD.org> In-Reply-To: <20061028002501.32f5b845@it.buh.tecnik93.com> References: <ehs1qk$6pa$1@sea.gmane.org> <cb5206420610270526p56bf0457i8e780b948a392d05@mail.gmail.com> <20061027231646.5b07bd8f@it.buh.tecnik93.com> <cb5206420610271404hbb3ba6an99377535ebe1af98@mail.gmail.com> <20061028002501.32f5b845@it.buh.tecnik93.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ion-Mihai IOnut Tetcu wrote:
> The problem with the OP's work is that some submitters/commiters think
> that the CVS commit message should document the _port_ changes while
> others think it should also document (or at least provide pointers) to
> the changes in the software itself
Good commit messages should do both.
On the other hand, there is no substitute for the user/admin thinking
for themselves. I think that if we try to overengineer making things
foolproof, the universe will simply conspire to create "better" fools.
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45464ADF.7040201>