When bitcoind can't bind, bitcoin server (or Bitcoin Core Daemon) is probably already running. Add the missing word "server". Bitcoin itself is definitely running ;-)
Add _(...) so the string can be localized.
I apologize for such trivial changes, learning github interface (if I'm doing something wrong, please tell me so, thank you).
When bitcoind can't bind, bitcoin server (or Bitcoin Core Daemon) is probably already running. Add the missing word "server". Bitcoin itself is definitely running ;-)
Add _(...) so the string can be localized.
I apologize for such trivial changes, learning github interface.
Can you make the commit message a bit more informative? (something like: clarify message when unable to bind port)
No need to apologize for trivial changes, making help and error messages more clear is worth it and, unlike other code changes, easy to review.
ACK
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/2d2d8fae3d8bc4e82dc631d93c6e19f954bbee04 for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
Next time please squash commits into one, for example using git rebase -i.
(if you have multiple small changes, submitting them as separate commits makes no sense)
Thanks, will try to do. I'm trying to use only github web UI to learn its possibilities...