meaning of '*' in bzr status is undocumented and unverbose
Bug #46636 reported by
James Troup
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Low
|
Unassigned | ||
| Breezy |
Triaged
|
Low
|
Unassigned | ||
Bug Description
The meaning of '*' in 'bzr status' output is undocumented. There also doesn't seem to be anyway to get bzr status to tell me _how_ the file mode has changed.
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in bzr: | |
| importance: | Medium → Low |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| Bojan Nikolic (bojan-bnikolic) wrote | #2 |
Revision history for this message
| Martin Pool (mbp) wrote | #3 |
| tags: | added: help status |
Revision history for this message
| Codename: Steeve Knight (cnsknight) wrote | #4 |
| tags: | added: check-for-breezy |
| tags: | removed: check-for-breezy |
| Changed in brz: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
It is rather minimal, though it relates to the same way that 'ls -F' shows a '*' for an executable file.
However, 'bzr diff' which is sort of a 'verbose version of status', also only states:
=== modified file 'bzr' (properties changed)
Without saying *how* the properties have changed.
Can you propose a possible text that would be helpful and make it clear what is going on?