qlog for multiple branches: need option to specify main branch

[Alexander Belchenko]

For review and merge process it's very useful to look at the history of 2 branches: main (trunk) and another one supposed to merge into trunk. For this purpose I'd like to see trunk branch as main (leftmost) branch with plain revnos and another branch as second branch with dotted revnos. It will be nice if qlog can accept some option, e.g. --main-branch or something similar so user can force some branch to be the leftmost. This can be useful for viewing several branches in shared repo as well.

Maybe (as an idea) qlog can keep the sequence of branches in the qlog window the same as in command line? Amy be this will be simpler approach?

[Gary van der Merwe (garyvdm)]

As to the second suggestion, I though that we were doing that. On investigation - I found that it was broken. I've fixed it now.

If you run bzr qlog repo, it chooses which branch is the trunk from the branch nick. It takes the first branch that has the nick "trunk" or "bzr.dev". This string is now translatable. It would be nice if it was also configurable.

It would be easy to add a command line argument. Just set log_list.graph_provider.trunk_branch before load_branch_heads is run.

[Alexander Belchenko (bialix)]

Gary van der Merwe пишет:
> As to the second suggestion, I though that we were doing that. On
> investigation - I found that it was broken. I've fixed it now.
>
> If you run bzr qlog repo, it chooses which branch is the trunk from the
> branch nick. It takes the first branch that has the nick "trunk" or
> "bzr.dev". This string is now translatable. It would be nice if it was
> also configurable.
>
> It would be easy to add a command line argument. Just set
> log_list.graph_provider.trunk_branch before load_branch_heads is run.

Thanks for the info. I'll look into this.

[Gary van der Merwe (garyvdm)]

There are ways to specify the main branch. You can either name the branch 'trunk', or pass it as the first argument. e.g.:

bzr loq repo/main repo

We need to improve the documentation to let users know this.