Exporting remote Bazaar branch creates unnecessary clone

[jelmer]

When creating an export of a remote Bazaar branch, pip currently will create a local clone of the branch, and then create an export from there.

This is unnecessary, as Bazaar supports directly exporting from a remote branch location - and this is significantly faster than first cloning, then exporting.

[matador86]

By default, branches in Git have nothing to do with each other. However, when you tell a local branch to "track" a remote branch, you create a connection between these two branches. Your local branch now has a "counterpart" on the remote server. Tutuapp 9Apps Aptoide

[jelmer]

@matador86 if only fetch some of the history ('git clone --depth X') then git won't automatically pull in history that's missing from remote branches. For example, 'git log' would only go X revisions back rather than to the beginning of history.

This discussion probably belongs on the pull request for git though, rather than this one (which is specific to bzr).

[zouhc]

By default, branches in Git have nothing to do with each other. However, when you tell a local branch to "track" a remote branch, you create a connection between these two branches. Your local branch now has a "counterpart" on the remote server. 9Apps