[wishlist] automatically set a branch nick to "tree_basedir/branch_name"

[Alexander Belchenko]

I really like that automatic nick appears in the log output, and for non-colo branches it points to something really useful, based on the basename of my working tree. So if I have committed in the tree resided in folder like "Bugfix-1234" or "Customer-ABC" or "Feature_XYZ" then I can see those descriptive nicks in the log.

But with colo most of my commits have "trunk" nick.

I wonder if it's possible for bzr-colo to automatically set explicit nick on colo-branch or colo-mv command to something like "tree_basedir/branch_name", so if I have colo workspace in the "Bugfix-1234" and I have plain colo-workspace then I'll have nick as "Bugfix-1234/trunk". When I create a new feature branch in that workspace it'll have nick as "Bugfix-1234/feature" or even maybe "Bugfix-1234/subdir/feature" (I mean that after Bugfix-1234/ there should be the same relative path as bzr colo-branches shows it).

I wonder if it's possible to do in a hook, so `bzr switch -b foo` in colo-workspace will set the proper nick too, but if it'll be only limited to colo-* commands, that'll be fine too.

[Jelmer Vernooij (jelmer)]

FWIW When I work with colocated branches, I usually keep the upstream branch in the "trunk" colocated branch, and create separate colocated branches for any feature work I do. The existing behaviour works well for this.