bzr status/commit/revert performance

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Arbash Meinel wrote:
> I'm not sure why reverting a newly added file needs to check the
> sha1sum, other than a possible layering issue.

If the file was added in a merge, and hasn't been modified since, revert
will delete it.  Otherwise, it will keep it.  We need the SHA1 in order
to determine whether the file has been modified.

But it does look like we could avoid it in this case, by checking
whether the file is in the merge_modified set first.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHhpWX0F+nu1YWqI0RAi/8AJ9IIElEjq46zqhIoQhmzq8u6kqptQCfcqC+
iqim+wta4ibUk8MuPgp6/5s=
=pFSa
-----END PGP SIGNATURE-----