orchestrator-client -h does not require parameters. This bug prevents help messages from being printed

[Fanduzi]

[root@centos-4 21:37:53 /usr/local/orchestrator]
#orchestrator-client -h
/usr/bin/orchestrator-client: option requires an argument -- h
orchestrator-client[80311]: No command given. Use orchestrator-client -c <command> [...] or orchestrator-client --command <command> [...] to do something useful

[root@centos-4 21:47:24 /usr/local/orchestrator]
#orchestrator-client --help
/usr/bin/orchestrator-client: option requires an argument -- h
orchestrator-client[80378]: No command given. Use orchestrator-client -c <command> [...] or orchestrator-client --command <command> [...] to do something useful

[root@centos-4 21:47:40 /usr/local/orchestrator]
#orchestrator-client -help
/usr/bin/orchestrator-client: option requires an argument -- h
orchestrator-client[80434]: No command given. Use orchestrator-client -c <command> [...] or orchestrator-client --command <command> [...] to do something useful

[root@centos-4 21:47:43 /usr/local/orchestrator]
#orchestrator-client -help T_T
Usage: orchestrator-client -c <command> [flags...]
Example: orchestrator-client -c which-master -i some.replica
Options:

  -h, --help
...

[Fanduzi]

@shlomi-noach Please review

[binwiederhier]

@Fanduzi Shlomi is taking a (possibly indefinite) break from orchestrator. I think you can probably consider it unmaintained as of today: http://code.openark.org/blog/mysql/reducing-my-oss-involvement-and-how-it-affects-orchestrator-gh-ost

I’m going to bring down my work volume around OSS to a minimum, specifically when it comes to orchestrator and gh-ost. This is to explain the whats and hows so that users are as informed as possible. TL;DR a period of time I will not respond to issues, will not review pull requests, will not produce releases, will not answer on mailing lists. That period of time is undefined. Could be as short as a few weeks, could be months, more, an unknown.

[Fanduzi]

@Fanduzi Shlomi is taking a (possibly indefinite) break from orchestrator. I think you can probably consider it unmaintained as of today: http://code.openark.org/blog/mysql/reducing-my-oss-involvement-and-how-it-affects-orchestrator-gh-ost

I’m going to bring down my work volume around OSS to a minimum, specifically when it comes to orchestrator and gh-ost. This is to explain the whats and hows so that users are as informed as possible. TL;DR a period of time I will not respond to issues, will not review pull requests, will not produce releases, will not answer on mailing lists. That period of time is undefined. Could be as short as a few weeks, could be months, more, an unknown.

Thank you @binwiederhier, It's realy a bad news