bzr rm {--force, --keep, --safe} is hard to use
Bug #400554 reported by
Marius Kruger
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Medium
|
Marius Kruger | ||
Bug Description
change behaviour to delete the files by default
* 'bzr rm foo' - will make foo unversioned and delete foo, making backups when necessary with the same rules 'bzr revert' uses.
* 'bzr rm foo --keep' - will only unversion (will not make backups).
* 'bzr rm foo --force' or 'bzr rm foo --delete' - will delete the file regardless if it is safe and will not make backups.
for further info/discussion see also:
http://
Related branches
lp:~amanica/bzr/backup-unsafe-rm-dont-complain-400554
- Vincent Ladeuil: Approve
- John A Meinel: Needs Fixing
-
Diff: 495 lines (+130/-127)8 files modifiedNEWS (+6/-0)
bzrlib/builtins.py (+6/-6)
bzrlib/bzrdir.py (+10/-8)
bzrlib/errors.py (+2/-0)
bzrlib/tests/blackbox/test_remove.py (+7/-18)
bzrlib/tests/per_workingtree/test_remove.py (+50/-57)
bzrlib/tests/test_bzrdir.py (+17/-0)
bzrlib/workingtree.py (+32/-38)
lp:~vila/bzr/integration
- Vincent Ladeuil: Approve
-
Diff: 31 lines (+4/-4)2 files modifiedbzrlib/lazy_regex.py (+3/-3)
doc/en/release-notes/bzr-2.7.txt (+1/-1)
lp:~amanica/bzr/rm-no-backup-400554
- Martin Pool: Approve
- Martin Packman (community): Approve
-
Diff: 102 lines (+40/-7)3 files modifiedNEWS (+5/-0)
bzrlib/builtins.py (+9/-2)
bzrlib/tests/blackbox/test_remove.py (+26/-5)
Revision history for this message
| Zearin (zearin) wrote | #1 |
| Changed in bzr: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Martin Pool (mbp) wrote | #2 |
| Changed in bzr: | |
| milestone: | none → 2.3b1 |
| status: | In Progress → Fix Released |
To post a comment you must log in.
I suspect this won't be received well because command line programs tend to prefer using --flags instead of confirmation dialogs, but…
What if you just asked the user "Delete, Keep, or Unversion? [Default: X]"