title: Mercurial: abandoning multiple, contiguous commits, on the `default` branch
body: <h1>Requirement</h1>
  
  <p>I'd like to abandon a line of development on the <code>default</code> branch, winding back to a revision from about 15 change sets back, and have <code>default</code> proceed from there.</p>
  
  <h1>My setup</h1>
  
  <p>This is a solo development project with one other guy testing infrequently. I push (frequently) to bitbucket for backups and sharing with the tester. Several of the changes I want to abandon are pushed to BitBucket.</p>
  
  <h1>Options</h1>
  
  <p>Any of these would be fine…</p>
  
  <ol>
  <li><p>The abandoned change sets to continue to exist in the repo. It would be nice if they could live on their own branch <code>abandoned-experiment-1</code>, say, that I can close and ignore, but this would need them to move on to a retrospectively created branch (which seems like it would be an awesome feature?).</p></li>
  <li><p>Some kind of merge to happen where I add a new revision to <code>default</code> that is the rollback to the revision I want to continue from.</p></li>
  <li><p>The change sets to be destroyed, but I suspect there's no way to achieve that without replacing the BitBucket repo and my tester's repo, which I'm not keen on.</p></li>
  </ol>
  
  <p>I'm not too sure how to evaluate which options are possible, which is best, or whether there are other, better options. I'm also not sure how to actually proceed with the repo update!</p>
  
  <p>Thank you.</p>