On Tue, 2008-03-25 at 12:04 +1100, Robert Collins wrote: > 'bzr revert' changes the working tree to be the same as a given revision > [with optional file list]. > If you then do a commit - e.g: > bzr revert -r X > bzr commit > you are committing a changeset that happens to alter previously done > work, but bzr does not consider this a cherrypick or merge - the undo > will propogate.
How does revert differ from a backout merge down to that same revision? bzr revert -r X bzr merge -r -1..X (or last:..X) Regards Henrik
