How do I update a working tree to an old revision?
aaron at aaronbentley.com
Fri Jul 17 13:39:38 BST 2009
-----BEGIN PGP SIGNED MESSAGE-----
Nicholas Allen wrote:
>> But it doesn't need that feature in order to be able to find the
>> revision where a bug was introduced. Revert will work just fine for
> I thought that revert with a -r argument will change the working tree so
> that committing would undo some changes.
It will. You weren't proposing to commit, you were trying to find a
bug. For the branch, that's a read-only operation.
update -r would make it impossible to commit anyhow, since the tree
would be out of date.
I don't understand how commit is relevant.
> If you do this multiple times
> it doesn't make much sense does it?
Reverting multiple times makes perfect sense. Each time, it restores
the files to the state they were in when the specified revision was
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the bazaar