(Back on this week-old message, sorry.)
If the "GNU coding standards" guidelines suggest not to include "why"
a change was made in a ChangeLog entry, then it should be corrected.
What they suggest is to include the reason for a change as a comment in
the code. From
http://www.gnu.org/pre
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Jim Meyering wrote:
>> I have found that it is useful to keep the commit log message
>> very similar to the ChangeLog entry.
>
> ... whereas I find it useful to put rationale information into the cvs
> commit message. (Because the ChangeLog entry is only su
Jim Meyering wrote:
> I have found that it is useful to keep the commit log message
> very similar to the ChangeLog entry.
... whereas I find it useful to put rationale information into the cvs
commit message. (Because the ChangeLog entry is only supposed to mention
_what_ has changed, not _why_.
