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

Bug #46636 reported by James Troup
Affects Status Importance Assigned to Milestone

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.

Tags: help status
Revision history for this message
John A Meinel (jameinel) wrote :

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?

Changed in bzr:
importance: Medium → Low
status: Unconfirmed → Confirmed
Revision history for this message
Bojan Nikolic (bojan-bnikolic) wrote :

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

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

- 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).

Revision history for this message
Martin Pool (mbp) wrote :

Almost a dupe of bug 112390?

Jelmer Vernooij (jelmer)
tags: added: help status
Revision history for this message
Codename: Steeve Knight (cnsknight) wrote :

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

Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
Jelmer Vernooij (jelmer)
tags: removed: check-for-breezy
Changed in brz:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.