bzr revert needs --no-recurse option

Bug #491223 reported by Alexander Belchenko
6
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.

Martin Pool (mbp)
Changed in bzr:
importance: Undecided → Medium
status: New → Confirmed
tags: added: easy
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

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.

Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 491223] Re: bzr revert needs --no-recurse option

Dmitrijs Ledkovs пишет:
> 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.

Maybe. But revert is usually much simpler to use, because I don't need
to type `bzr mv new-name old-name`, just `bzr revert`. Simple and beautiful.

> Associate bug in qbzr has been marked fix released in 2009 do we really
> need to have this option?
>
> Bzr is recursive by default.

Yes, it is. That's why some commands have --no-recurse option.

--
All the dude wanted was his rug back

Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.