bzr status provides only truncated log messages

[Steve Alexander]

When I use bzr status, the text of the pending merges' log messages is truncated.

There is no reasonable way to read just these log messages in full.

For example, bzr status could have a --wide option for this.

Also, the truncation is at some arbitrary number of characters, not the width of my terminal.

Rob Collins gives a workaround:

<lifeless> SteveA: for now, you should be able to do log -r revid:merged-revision-id
<lifeless> you can get that revision from .bzr/checkout/pending-merges

Which is rather complicated for an average user like me.

[Alexander Belchenko (bialix)]

I think it worth adding hidden command with name `pending-merges' that produce output similar to `log' or `missing' commands

[Martin Pool (mbp)]

Also, this can break test_pending if the terminal of the person running the test is very wide. I'm going to kludge that now by making the test data very wide.

Also, when the output is redirected to a file, there should probably not be any truncation.

I think the truncation should now be reliably at the terminal width.

[Per Johansson (per.j)]

A penging-merges command would be great. I just ran into the situation where I'd forgotten about my commit --local and did an update. If there'd been a way to find the revision id of my pending merge I might've been able to revert to it. The full log message had also been good for the new commit I had to do.