You are right, the problem is in loom. But the problem has nothing to do with changes to a loom, as I don't use looms in any of the branches I tried this with. So my guess is that this is a generic bug in loom that raises its ugly head each time "status" is invoked with a range of revisions.
You are right, the problem is in loom. But the problem has nothing to do with changes to a loom, as I don't use looms in any of the branches I tried this with. So my guess is that this is a generic bug in loom that raises its ugly head each time "status" is invoked with a range of revisions.
I have filed another bug report about that, https:/ /bugs.launchpad .net/bzr/ +bug/904095. Feel free to close this one.