Team packages maintained in bzr, one branch for the team or one for each debian directory?
lool at dooz.org
Mon Jul 30 11:28:35 BST 2007
On Mon, Jul 30, 2007, Robert Collins wrote:
> > The current implementation is very simple (for branch in iter():
> > pull()), but there are at least two solutions to help with speed:
> > 1) (already proposed) rewrite this to reuse a transport when possible
> This is the right approach.
Okay, I gave it a shot (see attached patch), all will propose this for
inclusion in bzrtools; I filed this under Debian's bzrtools package for
Not sure whether the old behavior should still be made available.
 following the advice at https://bugs.launchpad.net/bzrtools/+filebug
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3663 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/ubuntu-desktop/attachments/20070730/09086b35/attachment.bin
More information about the ubuntu-desktop