meaning of '*' in bzr status is undocumented and unverbose

[James Troup]

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.

[John A Meinel (jameinel)]

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?

[Bojan Nikolic (bojan-bnikolic)]

I got confused by the * for a minute too... Perhaps:

--- a/bzrlib/builtins.py
+++ b/bzrlib/builtins.py
@@ -135,7 +135,8 @@
         parent directory was renamed.

     modified
- Text has changed since the previous revision.
+ Text has changed since the previous revision. Trailing * indicates
+ execute permission has changed.

     kind changed
         File kind has been changed (e.g. from file to directory).

[Martin Pool (mbp)]

Almost a dupe of bug 112390?

[Codename: Steeve Knight (cnsknight)]

omg so is it a result of a chmod???
Useless info in st I'd say.