bzr revert needs --no-recurse option
Bug #491223 reported by
Alexander Belchenko
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned |
Bug Description
We'd like to have `revert --no-recurse` as `add --no-recurse` for QBzr needs (see Bug #491212 for example).
Another use case: I've renamed/moved directory and changed some files within it. I want to revert directory name changes, but keep changes of files.
Changed in bzr: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
tags: | added: easy |
tags: | added: check-for-breezy |
To post a comment you must log in.
If you want to revert the directory name change but not the files change in it you would do $ bzr mv again. If you have changed files in the top level dir you can just list them $ bzr revert file1 file2.
Associate bug in qbzr has been marked fix released in 2009 do we really need to have this option?
Bzr is recursive by default.