[PATCH stable] tests: test `clone --rebase` when local has mq patches applied

[timeless]

On Wed, Nov 3, 2010 at 6:49 PM, Kevin Bullock
<kbullock+mercurial at ringworld.org> wrote:
> IIUC the aforementioned error comes up when a pull results in tip being on a different branch—that is, when pull --rebase would _automatically and unexpectedly_ try to rebase the queue onto a different branch. Having a `pull` land you on a different branch seems like confusing behavior to be avoided. Or am I misunderstanding the issue?

In my case, I explicitly picked a target branch by using #syntax. I
thus "knew" what i wanted.

In the case of mq, the "branch" i'm on is generally irrelevant, and
thus it makes a lot more sense for me to want to move an mq to another
random branch when i do pull --rebase http://server/repo#branch