© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
So... my guess is that bzr-email is walking the whole ancestry to determine dotted revnos (it should only do this for commits of merge revisions, simple commits are logged differently).
However, if the remote branch is Stacked and bzr-email is on the server, then most likely it cannot access the stacked on branch (by design of the smart protocol...)
I don't have a good answer for this. The design for *clients* is that they will manually fall back to the stacked-on location to resolve things. But for bzr-email running *server side* it cannot do that....