title: Why does `git rebase` apply all of the commits rather than just applying the last one?
body: <p>I'm aware of how <code>git rebase</code> works, and I've been using it in production for a while.  It replays all of the commits of a branch onto another branch.  It rewrites history of your current branch.</p>
  
  <p>I've recently started playing around with <code>git rebase --skip</code>, although I was initially terrified of it.  I realize it just skips that commit as if it never happened.  </p>
  
  <p>It seems to me that the resulting <strong>working directory</strong> would be the same in these two cases:</p>
  
  <p>1)  all of the commits are skipped except the most recent</p>
  
  <p>2)  all of the commits are replayed, such that the commits are resolved in favor of <code>their</code> branch.  </p>
  
  <p><strong>Reminder</strong>:  <code>their</code> is the branch that you are currently on when you rebase.<br>
  <strong>Other reminder</strong>:  I'm specifically interested in the <em>working directory</em>.  Is this the same?</p>
  
  <p>Is it true that the working directory is the same result?  </p>