Merge lp:~amanica/bzr/rm-no-backup-400554 into lp:bzr
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Martin Packman | ||||
Approved revision: | no longer in the source branch. | ||||
Merged at revision: | 5465 | ||||
Proposed branch: | lp:~amanica/bzr/rm-no-backup-400554 | ||||
Merge into: | lp:bzr | ||||
Diff against target: |
102 lines (+40/-7) 3 files modified
NEWS (+5/-0) bzrlib/builtins.py (+9/-2) bzrlib/tests/blackbox/test_remove.py (+26/-5) |
||||
To merge this branch: | bzr merge lp:~amanica/bzr/rm-no-backup-400554 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Martin Pool | Approve | ||
Martin Packman (community) | Approve | ||
Review via email: mp+36612@code.launchpad.net |
Commit message
add 'bzr rm --no-backup' and deprecate the --force opting to be consitent with revert
Description of the change
This fixes the last bit of:
https:/
by adding a --no-backup to `bzr rm` and deprecating --force.
--no-backup is consistent with `bzr revert`
so now we don't need the big --force hammer any more.
* I didn't change the internal parameter names because I don't know if its worth the effort
of renaming it.
* The --force option still appears in the help because I can't see how to
hide one RegistryOption but still work as a enumish thing. If we have to
hide it, we should first implement this feature in another merge proposal.
* --force now prints out a deprecation warning, encouraging the user to rather use
--no-backup.
* Maybe I'm not making it clear enough that --no-backup will delete
everything you tell it to, with no going back.
Thanks for that, Marius.
62 + self.run_ bzr(['remove' , '--no-backup'] + list(files), ["deleted a", "deleted b", sDeleted( files)
63 + error_regexes=
64 + "removed b/c", "deleted d"])
65 + self.assertFile
This code is fine, but it would be easier to read and write if you used run_script instead, and no slower.