Contributing my annoyance at this issue of the launchpad bazaar plugin: when using lots of local branches, it's frequent that the parent of the branch B is a local branch A rather than a remote repository, and bazaar does not (as far as I know) provide a way to refer to some arbitrary ancestor. Neither does the stacking branch detection go more than one level up (it should traverse all local repositories until it finds a remote parent or push branch, not stop at the first parent).
As a result, when using lots of local branches one *has* to explicitly provide a stacking URL, and this becomes a strong annoyance with lots of short-lived branches, because one then has to hunt his disk for the right ssh url to the branch, due to lp: urls not being correctly expanded.
Contributing my annoyance at this issue of the launchpad bazaar plugin: when using lots of local branches, it's frequent that the parent of the branch B is a local branch A rather than a remote repository, and bazaar does not (as far as I know) provide a way to refer to some arbitrary ancestor. Neither does the stacking branch detection go more than one level up (it should traverse all local repositories until it finds a remote parent or push branch, not stop at the first parent).
As a result, when using lots of local branches one *has* to explicitly provide a stacking URL, and this becomes a strong annoyance with lots of short-lived branches, because one then has to hunt his disk for the right ssh url to the branch, due to lp: urls not being correctly expanded.