Bazaar

revert should be more informative

Bug #3707 reported by Björn Tillenius
2
Affects Status Importance Assigned to Milestone
Bazaar
Fix Released
Low
Unassigned
Bazaar 0.15

Bug Description

I reverted a file, and wondered why the file still showed up as modified when running bzr status. After a while, I discovered that I reverted an unmodified file with the same name, but in a different directory.

If I try to revert a file that is unmodified, I should get notified that the file didn't need to be reverted. Also, it'd be nice if it told me that when a file actually got reverted. It's good to get confirmation, so that it doesn't look like a no-op.

Revision history for this message
Robert Collins (lifeless) wrote :

mmm, it can get extremely noisy. If bzr revert 'foo' tells you that foo doesn't need reverting, then surely no output == not a no-op.

Robert Collins (lifeless)
Changed in bzr:
status: Unconfirmed → Needs Info
Revision history for this message
Martin Pool (mbp) wrote :

I think revert should be able to give verbose output similar to commit/merge/status. If it's the default for them it should be on for revert too.

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

Actually two issues

1 - 'revert -v' should tell you what's being done (or maybe that should be the default?)
2 - if you try to revert an unmodified file (or a dir with no changes inside, etc) then you should get a warning

Changed in bzr:
status: Needs Info → Confirmed
Aaron Bentley (abentley)
Changed in bzr:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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