title: How do I rebase in mercurial without merging?
body: <p>When I try to <code>hg rebase -s 1775 --collapse</code>, I am asked to merge all the files I touched since rev 1774.  How can I avoid that?</p>
  
  <p><strong>Details</strong></p>
  
  <p>I am just learning how to rebase.  I successfully tried the example given <a href="http://seanerussell.blogspot.com/2009/07/mercurial-rebase.html" rel="nofollow noreferrer">here</a>, and a few minor variations.  However, in my own repository, when I try the same steps, I am asked to merge a boat-load of files when I rebase.  Here's what I do.  What am I doing wrong?</p>
  
  <pre><code> hg update -r 1774
   hg tag "Started-New-Feature"
   hg rebase -s 1775 --collapse
  </code></pre>
  
  <p>I thought maybe it was because I had updated to -r1774, so I updated to tip after tagging -r1774.  Same result.  </p>
  
  <pre><code>hg update -r 1774
  hg tag "Started-New-Feature"
  hg update
  hg rebase -s 1775 --collapse
  </code></pre>
  
  <p>The <code>hg tag</code> creates a new rev -r1784.  So I tried updating specifically to -r1783.  Same result.</p>
  
  <pre><code>hg update -r 1774
  hg tag "Started-New-Feature"
  hg update -r 1774
  hg update -r 1783
  hg rebase -s 1775 --collapse
  </code></pre>
  
  <p>I've searched the web and SO for related questions and didn't find anything, which doesn't mean answers don't exist.  Pointers to existing answers are welcome.</p>
  
  <p><strong>Edit:</strong></p>
  
  <p>This seems related <a href="http://mercurial.selenic.com/bts/issue1561" rel="nofollow noreferrer">to a reported mercurial bug</a> that was fixed in 1.4.  I have version 1.1.  I tried updating to 1.4 or later, but <code>sudo apt-get install mercurial</code> says I have the latest, and the download link <a href="http://mercurial.selenic.com/" rel="nofollow noreferrer">on the mercurial page</a> is currently broken.  So maybe the answer is just getting the latest version, but hopefully there's another way around this.</p>