Incomprehensible results of "bzr log -rX..Y" again

[GuilhemBichot]

Taken out of the last comments in https://bugs.launchpad.net/bzr/+bug/474807, for clarity.
A colleague has a case which I cannot explain.
I get https://code.launchpad.net/~mysql/mysql-server/mysql-next-mr-bugfixing
and do, in order to see the ancestry of a revision:
bzr --no-plugins --no-aliases log -n0 -r 'revno:1..revid:<email address hidden>'
(same scenario as Bug 519862 by the way).
This returns 2300+ more revisions than the following bullet-proof way:
bzr branch -r 'revid:<email address hidden>' --no-tree . ../tmp
cd ../tmp
bzr --no-plugins --no-aliases log -n0 -r 'revno:1..revid:<email address hidden>'

Those 2300 additional revisions seem to be revisions which landed into the mainline in the same merge as sven.etc.

Is it normal that the first command returns revisions which are in fact not in the ancestry of sven.etc?
Is it explained by "bzr help log"?

[GuilhemBichot (guilhem-bichot)]

With revno 5204 I see that this is fixed, with the exception that the two commands return revisions in different orders when testing the above commands with https://code.launchpad.net/~mysql/mysql-server/mysql-next-mr-bugfixing. Same set of revisions is returned, just different order. I can't see why, but maybe it's not a big deal.

[Vincent Ladeuil (vila)]

The order is still the one provided by merge_sort so it can be different if the branches merged the revisions in different ways.

[GuilhemBichot (guilhem-bichot)]

looks like this bug can be closed.