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 Studio at the same time) but I think I will be
able to settle down to one change=one branch pretty soon.
Henry
On 5/27/2016 8:06 AM, Alex Shroyer wrote:
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'm encouraging people to use the "GitHub Desktop" app. For most
people its UI is preferable to the command line, and it does a good job of
making the most common git tasks more intuitive.
-Alex
On Thu, May 26, 2016 at 6:57 PM, bill lam <bbill....@gmail.com> wrote:
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 used to refer to the m$ c compiler for 20 years,
and predated visual studio.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
