title: git rebase --onto : not doing what I thought it does
body: <p>So, I'm obviously not using the commands properly, but I am having trouble figuring out exactly <em>which</em> command I need to type to achieve what I want to do:</p>
  
  <p>Consider a sprint branch, let's call it <code>Team_Sprint_5</code>.  On day 1 of the sprint, I create a new branch to work my issue: <code>Issue-1234-branch</code>.  So far, so good. My branch has a base of the <code>Team_Sprint_5</code> branch:</p>
  
  <p>Commit History at Branch Creation:</p>
  
  <pre><code>5825d  &lt;-- Team_Sprint_5 &amp; feature branch head
  3fc55  older commit
  a3911  even older commit
  </code></pre>
  
  <p>So, I do a commit. Now my branch looks like this:</p>
  
  <pre><code>2c442  &lt;-- My commit
  5825d  &lt;-- Issue-1234-branch Base
  3fc55  
  a3911
  </code></pre>
  
  <p>Meanwhile, the main sprint branch has been updated. <strong>I would like to move my branch to be at the tip of the current sprint branch</strong>:</p>
  
  <pre><code>(2c442) &lt;-- I want my commit to move here
   b6740  &lt;-- updated Team_Sprint_5 head
   a77fb
   ...    &lt;-- several additional commits in the main branch
  [2c442] &lt;-- where my commit ends up instead
   5825d  &lt;-- Where we originally started 
  </code></pre>
  
  <p>So, from my current branch, I used <code>git rebase --onto b6740</code>. However, that seemed to smash all the commits between my initial branch creation on top of the commit made in my branch, which is not what I intended. <strong>What is the appropriate command to do what I need?</strong></p>
  
  <p><strong>Edit:</strong>
  What I ended up doing, since I messed up my branch beyond my simple ability to fix it, is to create a new branch from the tip of the current sprint branch, then picked my commit using the <code>cherry-pick</code> command. I have to believe this can be done with a simple rebase on the original branch though.</p>