want an option to disable automatic removal of missing files in commit
Bug #488670 reported by
Martin Pool
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
The default behaviour of "commit" is to remove (unversion) files that have already been deleted locally, even if they weren't deleted 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, provided everyone does "bzr status" before committing it may not be too much of an issue.)
| Changed in bzr: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| tags: | added: commit |
| tags: | added: easy |
| description: | updated |
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 488670] [NEW] want an option to disable automatic removal of missing files in commit | #1 |
| tags: | added: check-for-breezy |
To post a comment you must log in.
I'm pretty sure this is a dup of a very very old bug - one that I put a
patch up for in fact.
-Rob