© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
So here's one approach to fixing this:
When processing an import branch X, if the default stacked on branch for branch X's target is also an import branch of the same type, arrange to pass the id of the default stacked on branch to the worker that processes branch X.
When a worker is passed a branch id to stack on, when it creates/clones the local branch to work into, it stacks it on the designated branch in the central store.
When the import is done, the worker should ensure that the branch in the central is also stacked (using a relative path!) on the stacked-on-branch in the central store, and the puller should also stack the branch on the central store.
None of this sounds too terribly difficult, which is good.