> Sure (I would like to see a convention where such explanations are > put in the commit messaage, but I have previously been outvoted on > that issue):
No, please don't put explanations into the commit message. But do put them into the source code as a comment. I'm also working on other projects, some of which do what you propose. What I often end up having to do there is do git blame, then git log for each line, in order to find out why the source code does what it does. Let's not do that here. There's a perfectly good inline mechanism for it: Comments.
