> I think that sort of metadata is more appropriate for an RT ticket. A > commit messages should describe primarily * what* is being changed > instead of *why* the change is being made. Of course, including the > *why* doesn't hurt but I don't believe it should be part of our > guidelines.
(This isn't at all my call, I know, but this is one of those things I have very strong opinions about.) I disagree very strongly. _What_ you're changing is something that's really easy to reverse-engineer from the diffs. _Why_ you you changed a dot to a colon or sorted a MANIFEST isn't something that anyone's going to be able to guess without a hint later on. "Why" is the one thing I really care about in Commit messages. Jesse
