I'm going to apologize in advance for the two commits coming up,
'oldbugs' and 'oldbugs2'. Each of these fixes quite a few old bugs, and
you will have to read the detailed commit message to see what.
I have excuses (basically my being overwhelmed by encountering the J
source, git, and Visual
Hey, I'm also known as hoosierEE on GitHub, and was flattered to see my
commit messages among the good examples, though I must admit the quality of
the messages on my own projects (where I'm usually the only contributor)
aren't nearly as good on average. See also: https://xkcd.com/1296/
At work I
I know the recommendation for commit message is subject + blank line +
paragraph, but since we worked on a very small team so that it was not so
important. We are still adjusting to a wider audience.
But I am quite surprised that msvc can be mistaken to "Mystery SerViCe".
The name should have been
We (particularly me) need to be be better at commit messages.
Working with a group of 0 or 1 or 2 who have long engagements with the
source make one sloppier than is good.
Also, being unfamiliar with git probably has some of us focusing more on
getting the raw mechanics right, than properly doing
