title: moving committed (but not pushed) changes to a new branch after pull
body: <p>I've done a fair bit of work ("Your branch is ahead of 'origin/master' by 37 commits.") which really should have gone into its own branch rather than into <code>master</code>.  These commits only exist on my local machine and have not been pushed to <code>origin</code>, but the situation is complicated somewhat in that other devs have been pushing to <code>origin/master</code> and I've pulled those changes.</p>
  
  <p>How do I retroactively move my 37 local commits onto a new branch?  Based on the docs, it appears that <code>git rebase --onto my-new-branch master</code> or <code>...origin/master</code> should do this, but both just give me the error "fatal: Needed a single revision".  <code>man git-rebase</code> says nothing about providing a revision to <code>rebase</code> and its examples do not do so, so I have no idea how to resolve this error.</p>
  
  <p>(Note that this is <strong>not</strong> a duplicate of <a href="https://stackoverflow.com/questions/1394797/git-how-to-move-existing-work-to-new-branch">Move existing, uncommited work to a new branch in Git</a> or <a href="https://stackoverflow.com/questions/556923/git-how-to-merge-my-local-working-changes-into-another-branch">How to merge my local uncommitted changes into another Git branch?</a> as those questions deal with uncommitted changes in the local working tree, not changes which have been committed locally.)</p>