Description of problem:
oc sub-command should remain useful help info from kubectl sub-command. Because for some sub-commands, `oc sub-command -h` trims the more detailed/clearer description/examples from kubectl, which may be important to user.
E.g.
oc proxy -h VS kubectl proxy -h
oc patch -h VS kubectl patch -h
oc run -h VS kubectl run -h

Version-Release number of selected component (if applicable):
oc v1.3.0-alpha.2-332-g8aaba51
kubernetes v1.3.0-alpha.3-599-g2746284

How reproducible:

Steps to Reproduce:
Just takes some sub-commands as instance:
1. oc proxy -h VS kubectl proxy -h
2. oc patch -h VS kubectl patch -h
3. oc run -h VS kubectl run -h

Actual results:
1.
See https://bugzilla.redhat.com/show_bug.cgi?id=1344877#c3 . Reference to bug 1344877 just wants to say, trimmed info in `oc proxy -h` causes user misunderstanding

2.
kubectl patch -h has more info than oc patch -h, such as more detailed examples about more flags

3.
kubectl run -h has more useful examples, such as about '--command` specified or not

Expected results:
oc sub-commands should remain useful help info from kubectl sub-command

Additional info:
Remaining useful help info from kubectl sub-command could be used TOGETHER with adding help info to oc. E.g. it is good for 'oc logs -h' to add statements about bc/build than 'kubectl logs -h'