title: Mercurial equivalent of svn's merge --record-only?
body: <p>We've recently moved our codebase from subversion to mercurial, and are doing our first release to production from the mercurial codebase this weekend.</p>
  
  <p>We have a three repo setup, let's call them <em>dev</em>, <em>stable</em> and <em>release</em>, where <em>dev</em> is a clone of <em>stable</em> and <em>stable</em> is a clone of <em>release</em>. At the moment, <em>dev</em> has our version 7 code, and <em>stable</em> has our version 6 code. We've just pushed the version 6 code to <em>release</em>. Our next release, version 6.1, is scheduled for next week.</p>
  
  <p>The problem is that, since we're also doing a major upgrade in the v6 release, we're expecting to release multiple times (6.0.1, 6.0.2, etc) before the 6.1 release. Going forward this won't be a problem as all three repos will have different version numbers, but right now both <em>stable</em> and <em>release</em> are v6.</p>
  
  <p>If I change the version numbers in our poms on <em>stable</em> to 6.1, this change will have to be pulled back to <em>dev</em>, which will mean fixing it there before any of those artefacts can build (so as to not pollute the v6.1 release with what are really v7 artefacts).</p>
  
  <p>Is there a way to tell mercurial to pull this change into <em>dev</em> without actually accepting the change, similar to what svn's merge --record-only does? Is the only option to pull the change to <em>dev</em> and then do a backout?</p>
  
  <p>Thanks</p>