Rant about ChangeLog entries and commit messages

[Robert Kiesling]

> Nicholas Nethercote <njn@csse.unimelb.edu.au> writes:
> 
> > Commit logs are basically invisible;
> 
> That's just a (fixable) problem in your coding setup. In other
> projects it is very common to use tools like cvs annotate / cvsps /
> git blame / git log / etc. to find the reasons for why code is the way
> it is. In fact in several editors these can be functions on hot
> keys. Programming is hard enough as is without ignoring such valuable
> information sources. Don't do it.

Unless there's a good reason _not_ to derive from a source, and there
are several, most of which require a clean-room approach, or a
simulation of it.  I'm just now starting to move over to Subversion,
and I'm sure it has the same ability, to publish CVS logs, though not
via CVS itself.  
C-x v u :)

-- 
Ctalk Home Page: http://www.ctalklang.org/