status, commit, merge, pull, push should give context in checkouts
Bug #420218 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
High
|
Unassigned | ||
Breezy |
Triaged
|
High
|
Unassigned |
Bug Description
Checkouts are different from branches - they do action-
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
--
tags: | added: ui |
tags: | added: check-for-breezy |
tags: | removed: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → High |
To post a comment you must log in.
2009/8/28 Robert Collins <email address hidden>: at-a-distance.
> Public bug reported:
>
> Checkouts are different from branches - they do action-
>
> 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 //example. com/foo
to branch bzr+ssh:
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.
-- launchpad. net/~mbp/>
Martin <http://