changesets and files in bzr vs cvs

[Talden]

> I tend to be more anal about documentation then many
> of my colleagues but I like to record both a summary
> "fix bug X" and an explanation (skipped when obvious)
> about how it was fixed that relates to the actual lines
> changes.  I suppose it could be argued that that information
> is more appropriate for code comments.

Hmm.. I think it was a git tutorial saying that git promotes a commit
message convention of a <=80 character first line summary followed
optionally by a blank line and then a longer summary message.

Of course I still wouldn't expect a line by line summary - that is
definitely code-commenting country but sometimes it is good to outline
the method behind the fix/feature and that can be helpful in the
commit message.

--
Talden