Comment 0 for bug 476293

Revision history for this message
GuilhemBichot (guilhem-bichot) wrote : "bzr log -rX..Y" gives output which does not contain X

Hello. Another report, after 474807 filed recently.
My initial intention here was too see whether bzr can be used to tell if a revision Y is a child of X; I expected that "bzr log -rX..Y" would fail if Y is not a child of X. So I did experiments, below.
I grab this branch: https://code.launchpad.net/~mysql/mysql-server/mysql-6.0-codebase-bugfixing
and I do
bzr log -n0 --show-ids -r tag:clone-5.2..tag:mysql-5.1.39
I expected an error, as mysql-5.1.39 is not a child of clone-5.2. I got no error, and the displaid log contains lots of revisions, including tag:clone-5.2 and tag:mysql-5.1.39. I wonder if "no error" is normal, I expected to trigger "bzr: ERROR: Start revision must be older than the end revision" (but when I look at the code which can emit such error, I see it compares revnos; with revnos being dotted numbers, I cannot see how they can reliably be compared).
Then I tried the reverse order:
bzr log -n0 --show-ids -r tag:mysql-5.1.39..tag:clone-5.2
I expected an error, as clone-5.2 is not a child of mysql-5.1.39. I got no error, and this time the displaid log contains tag:clone-5.2 but NOT tag:mysql-5.1.39, which sounds weird (how come the start bound is not included?).
Bazaar (bzr) 2.1.0dev3
  from bzr checkout /home/mysql_src/logiciels/bzr_versions/bzr.dev
    revision: 4782
    revid: <email address hidden>
    branch nick: bzr.dev