bzr branch-related commands should prevent confusion when a out of date working tree is present
Bug #107126 reported by
Robert Collins
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
| Breezy |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
affects /products/bzr
status confirmed
importance high
Currently it is possible for several commands - e.g. 'missing', 'log',
'revno' to show accurate data that does not help diagnose a problem.
Recently a user had an out of date pqm-submit tree, with up to date
branch, and didn't realise that this was the case. If 'log' or 'missing'
had provided an indicator of this it would have saved much confusion.
-Rob
--
GPG key available at: <http://
Revision history for this message
| Matthew Fuller (fullermd) wrote | #1 |
| Changed in bzr: | |
| importance: | High → Medium |
| tags: | added: checkout ui |
| tags: | added: check-for-breezy |
| tags: | removed: check-for-breezy |
| Changed in brz: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| importance: | Critical → Medium |
To post a comment you must log in.
This is tied in with an issue on my UIIssues page under the heading "Working tree awareness of what version it's at". The closest thing we have to a way to find the working tree's version is by looking at 'info' and doing math based on how many revisions out of date it says the tree is, and that's not even useful when your WT revision isn't on the mainline.