"bzr branches" should list colocated branches if supported

Bug #826820 reported by Jelmer Vernooij
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Fix Released
Medium
Jelmer Vernooij
BzrTools
Invalid
Medium
Jelmer Vernooij

Bug Description

The fact that the current implementation in bzrtools scans the file system seems to be confusing a lot of users, especially because it takes a fair amount of time to run.

Now that there is support for colocated branches in the core, it would also be nice to be able to list all colocated branches without requiring a plugin. I think "bzr branches" should by default just call list_branches() on the current control directory, rather than recursively searching the file system.

Perhaps the existing "bzr branches" can be renamed to e.g. "bzr discover-branches"?

Related branches

Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 826820] [NEW] "bzr branches" should list colocated branches if supported

+1

Revision history for this message
John A Meinel (jameinel) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8/16/2011 4:34 AM, Martin Pool wrote:
> +1
>

I think, in general, 'bzr branches' should be a core command (possibly
'bzr discover-branches'). And we can iterate on making it more
performant, etc.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5KKGUACgkQJdeBCYSNAAPnMACgz10TTX/7HsFsontbvIPM2oLA
h+sAnR4wFWk9tNDpe6KMTNwSJNJkip77
=yDqN
-----END PGP SIGNATURE-----

Vincent Ladeuil (vila)
Changed in bzr:
status: Triaged → Fix Released
milestone: none → 2.5b1
assignee: nobody → Jelmer Vernooij (jelmer)
Jelmer Vernooij (jelmer)
Changed in bzrtools:
status: New → In Progress
assignee: nobody → Jelmer Vernooij (jelmer)
Jelmer Vernooij (jelmer)
Changed in bzrtools:
status: In Progress → Fix Committed
importance: Undecided → Medium
Jelmer Vernooij (jelmer)
Changed in bzrtools:
status: Fix Committed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.