How to avoid commit removing files automatically?

Asked by Gareth White

The default behaviour of "commit" is to remove (unversion) files that have already been deleted locally, even if they weren't delete via the "remove" command. Is there a way to disable this behaviour? I'm thinking something similar to how "--strict" prevents committing with unknown files.

It just seems a bit dangerous for it to automatically assume a file that's not there at commit time was actually intended to be unversioned. A user or some script could inadvertently delete a file from disk and accidentally commit the change. Having an option to prevent the commit in this scenario could be useful.

(Then again, maybe I'm just too used to how ClearCase works. Provided everyone does "bzr status" before comitting it may not be too much of an issue.)

Question information

Language:
English Edit question
Status:
Solved
For:
Bazaar Edit question
Assignee:
No assignee Edit question
Solved by:
Martin Pool
Solved:
Last query:
Last reply:
Revision history for this message
Martin Pool (mbp) said :
#1

There is no such option at the moment. It would be useful.

Revision history for this message
Best Martin Pool (mbp) said :
#2
Revision history for this message
Gareth White (gwhite-deactivatedaccount) said :
#3

Thanks Martin Pool, that solved my question.