One is to be able to go back and look at the code that changed in a given
file over time. The other is to look at the checking commentary that was
included when those files were checked in. The first (which I think is what
you are talking about) is easily done. The second sort of requires a policy
choice. The commentary is just strings, but these strings have to hang off
of something. If you force people to enter them per-file, you tend not to
get overview. Conversely, if you key them per change, it's easy to fail to
get commentary on specific files.
My immediate question is which kind of object a checkin comment string
should hang from: a revision or a file. At the moment, it hangs off of a
revision. I'm inclined to think that's the better choice, but I wanted other