status, commit, merge, pull, push should give context in checkouts

[Robert Collins]

Checkouts are different from branches - they do action-at-a-distance.

Judging by what UI's building on bzr are doing, showing people the
actual branch that is being affect by a command is desirable.

 affects bzr
 importance high
 status confirmed

--

[Martin Pool (mbp)]

2009/8/28 Robert Collins <email address hidden>:
> Public bug reported:
>
> Checkouts are different from branches - they do action-at-a-distance.
>
> Judging by what UI's building on bzr are doing, showing people the
> actual branch that is being affect by a command is desirable.

It could be reasonable to show

  commiting from ~/bzr/foo
  to branch bzr+ssh://example.com/foo

and similarly for push, pull, etc

I don't really see the case for status - it just compares the tree to
it's basis - but then I rarely work in this mode.

--
Martin <http://launchpad.net/~mbp/>

[Robert Collins (lifeless)]

On Thu, 2009-08-27 at 23:36 +0000, Martin Pool wrote:
> ...but then I rarely work in this mode.

Given our upcoming UI refresh plans, I think it would be benficial if as
many of our devs as possible have spent a few weeks working with
lightweight checkouts.

-Rob