title: Mercurial: Concrete examples of issues using hg pull --rebase
body: <p>I'm struggling to find the mercurial workflow that fits the way that we work.</p>
  
  <p>I'm currently favouring a clone per feature but that is quite a change in mindset moving from Subversion. We'll also have issues with the current expense we have in setting up environments.</p>
  
  <p>Using hg pull --rebase seems to give us more of a Subversion-like workflow but from reading around I'm wary of using it.</p>
  
  <p>I think I understand the concepts and I can see that rewriting the history is not ideal but I can't seem to come up with any scenarios which I personally would consider unacceptable.</p>
  
  <p>I'd like to know what are the 'worst' scenarios that hg pull --rebase could create either theoretical or from experience. I'd like concrete examples rather than views on whether you 'should' rewrite history. Not that I'm against people having opinions, just that there already seem to be a lot of them expressed on the internet without many examples to back them up ;)</p>