Closed bulk88 closed 10 years ago
Thanks, I have merged this and plan to make a dev release.
One note: it is traditional to make commit message have a short first line (shown in the "oneline" format of a commit) followed by a blank line, followed by the rest. I have rewritten the first commit to be in that form.
About the first commit, in my GUI for git, I thought "WinCE fix, .gitignore, inlining, unused var removal, PERL_NO_GET_CONTEXT" made the title limit with a char or 2 to spare.
The problem was not the first line (although I did trim it down just a tad) but the lack of a blank line between it and the second line ( - ret became unused...
)
Every leading non-blank line is joined by space for presentation in short form so that:
This seems like a short commit message.
...but it's actually long
will show up in short log as:
This seems like a short commit message. ...but it's actually long
So you need to write:
This seems like a short commit message.
...but it's actually short.
I used a different view in my GUI for git (more console like, not strip the blank line, show first line in bold and indent first line), and I see what I did, it was a typo. The lack of the blank line was because I copy pasted the change log into the commit message and edited it and forgot to add a blank line.
The .gitignore could be better but I couldnt find any good cross platform examples for EUMM mods, Tested on Win32 VC blead, Win32 VC 5.12 DEBUGGING, Win32 Strawberry GCC 5.8, FWIW my Win32 VC 5.6 test failed with