OK. Having read that I still don't see how this use case differs enough
from creating the branch via git push to justify having a new SSH
command for it.
Current workflow:
1. Create the branch: git push origin master:refs/heads/new-branch
2. Push commits for review: git push origin HEAD:refs/for/new-branch
Workflow with SSH command:
1. Create the branch: ssh -p 29418 user@review gerrit create-branch [...]
2. Push commits for review: git push origin HEAD:refs/for/new-branch
In both cases the branch needs to be created before commits can be
pushed for review.
The only difference I can see is that with the ssh command the user is
limited to creating the branch, and cannot push changes into it at the
same time.
> <
https://mail.nokia.com/owa/redir.aspx?C=9xmSUGNtgEy91Z-nzA78gDRrkhrrwtAI7GPEEfwCQzXFJe4Zh_uZTFzXLHkVSDGmpbYhnweAS9E.&URL=https%3a%2f%2fcode.google.com%2fp%2fgerrit%2fissues%2fdetail%3fid%3d1156>
>
Note that your link redirects to Nokia's webmail server :)