On Mon, Dec 03, 2007 at 10:02:13AM +1100, Ben Elliston wrote: > Having said that, I find the lack of rationale for some changes to be a > bit irritating. I know that this should be done through code comments, > but those are often made across the changeset and in different files. > There is rarely a single summary of the need for the change. It would > be nice to consider a practice similar to that used by NetBSD, which is > to use a paragraph or so describing the need for the change (similar to > what we do when we introduce a patch on gcc-patches) and inserting that > comment into the svn commit message.
Or even into the ChangeLog... I've worked on other projects that did this. I found it incredibly helpful. -- Daniel Jacobowitz CodeSourcery