BTW, the README version in your fork was 6 commits behind master so I had to resolve conflicts before merge. Since you probably might be contributing more in the future, you can add this repo as an upstream repo in your config
(or use the HTTPS url if that's what you prefer). Then you can fetch the latest commit with git pull upstream master and then add your changes to your branch (unless you explicitly want to start changes from an earlier commit). Then when done, you do git push origin <your branch> and then submit the PR so that it is easier to compare and merge :)
Thanks @halirutan! I've rebased this to master as commit 409ee87cfdbc3428338e7d691822a625fb2c13f5. (I made a couple of tiny word corrections before merging.)
BTW, the README version in your fork was 6 commits behind master so I had to resolve conflicts before merge. Since you probably might be contributing more in the future, you can add this repo as an upstream repo in your config
(or use the HTTPS url if that's what you prefer). Then you can fetch the latest commit with
git pull upstream masterand then add your changes to your branch (unless you explicitly want to start changes from an earlier commit). Then when done, you dogit push origin <your branch>and then submit the PR so that it is easier to compare and merge :)