remember update the ChangeLog!
This is just a reminder to update the ChangeLog file whenever you commit something to CVS!
This is really important! Otherwise at minimum it's hard for everyone to see what everyone else is working on.
-mental
By the way, there's a tool called cvs2cl that generates a summary of cvs commits in changelog style. This can be useful for helping make sure the official Changelog contains all the right info, and of course detecting who is and is not keeping their Changelog comments up to date.
Bryce
On Tue, 13 Jan 2004, MenTaLguY wrote:
This is just a reminder to update the ChangeLog file whenever you commit something to CVS!
This is really important! Otherwise at minimum it's hard for everyone to see what everyone else is working on.
-mental
On Tue, Jan 13, 2004 at 11:03:04PM -0500, MenTaLguY wrote:
This is just a reminder to update the ChangeLog file whenever you commit something to CVS!
This is really important! Otherwise at minimum it's hard for everyone to see what everyone else is working on.
Clarifying "everything" ("whenever"):
We have two places for describing changes: the ChangeLog and cvs commit messages.
To my knowledge we don't yet have standards for what to put in these two channels; though the Gnu coding standards would be a starting point on what to put in ChangeLogs (*see (standards)Change Logs).
The `Simple Changes' node has a few comments on what can be omitted or referred to tersely ("All callers changed.") in ChangeLog.
A reason for ChangeLog entries being either terse or omitted would be to make it faster to find more valuable information.
Whitespace-only changes may be another example of something that may be either tersely mentioned or omitted from the ChangeLog. (If omitted, there'd still be a commit message for the change/s.)
pjm.
participants (3)
-
Bryce Harrington -
MenTaLguY -
Peter Moulder