list all branches in a shared repository

The bzrtools plugin <http://bazaar-vcs.org/BzrTools> has a "bzr branches" command that does about what you want. It scans a directory tree for branches, whether or not they are in shared repositories.

BTW, if you want to run e.g. "bzr branches bzr+ssh://whatever", you can (as long as you're not trying to do it over plain http), but it's very inefficient. You should log into the server through ssh or something and run it locally.

thanks for the speedy answer!

Thanks Matt Nordhoff, that solved my question.

Hello, this apparently does not work with bzr 2.6.

You need to have bzrtools installed, and use the bzr branches command from bzrtools. There is a 'bzr find-branches' alias I think.

bzrtools is installed via apt:

$bzr help bzrtools
Various useful commands for working with bzr.

$bzr find-branches ftp://myserver.com
bzr: ERROR: Unbekannter Befehl »find-branches«

$bzr branches ftp://myserver.com
nothing returned.

Has the command changed?
It had worked before.

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

bzr is really a pain. Isn´t anybody able to answer the question of the original poster?

unsubscribe.

> bzr is really a pain. Isn´t anybody able to answer the question of the original poster?

Try reading again, the first answer given is right to the point.

Since then 'bzr branches' became a core command with a few rough edges. Jelmer's answer is a "safe" answer without more precise information from the original poster (does it fail only against a remote server, does it fail/work locally, whatever).

If you feel differently and know better, feel free to provide a better answer.

If you're not, what's your point ?

bzr doesn't fit your needs ? Can you think of a better question than 'bzr is really a pain' that gives exactly zero information about why *you* think so nor allows anybody to provide any useful answer ? And that's if they were not discouraged (not to say offended or disgusted) by your approach of the problem...

And do you think your comment is even appropriate here ? What did you expect to find on this page ?

@martin: I kind of imagine why you wrote 'unsubscribe', but it's still a bit ambiguous ;-D