Doing away with changelogs

Ken Raeburn raeburn at MIT.EDU
Wed Apr 19 16:45:47 EDT 2006

> What is useful is a description of the code change, just as one
> would write for a commit message.
> Really, that's all we're asking for.  But people keep interpreting  
> that
> request as needing to do some complex task involving integration  
> with bug
> databases and manual massaging for each release.

Does that mean we should just have this log include the "clean up  
whitespace" and "fix typo in comment" and "run 'make depend' again"  
and "oops, back out the part of that change I didn't mean to check  
in" messages that inevitably wind up in such a list?

More information about the krbdev mailing list