bzr itself already remembers URL's. So once someone has the code they won't need the hint :). However, I think you mean 'tell someone who does not have the code how to get it'. I think that that is a good idea. This just needs loggerhead to know the public_branch of each branch - and bzr already has the configuration glue to set that as a default policy
set in ~/.bazaar/locations.conf
would allow loggerhead to call 'branch.get_config().public_branch()' (or something like that - just sketching) and thus know the url to present to users.
I would recommend starting with 'bzr branch' as the command shown, simply because that is the mode of operation most users will need most of the time.
bzr itself already remembers URL's. So once someone has the code they won't need the hint :). However, I think you mean 'tell someone who does not have the code how to get it'. I think that that is a good idea. This just needs loggerhead to know the public_branch of each branch - and bzr already has the configuration glue to set that as a default policy
e.g. //srv/bzr/ gnome] bzr-mirror. gnome.org branch: policy = appendpath
[file:/
public_branch = http://
public_
set in ~/.bazaar/ locations. conf get_config( ).public_ branch( )' (or something like that - just sketching) and thus know the url to present to users.
would allow loggerhead to call 'branch.
I would recommend starting with 'bzr branch' as the command shown, simply because that is the mode of operation most users will need most of the time.