refactoring and noting mv/rename after the fact

[Aaron Bentley]

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

John Yates wrote:
| On Monday, April 11, 2005, Aaron Bentley wrote:
|
|
|>Ultimately,
|>rename(2)s don't always mean what they look like (because they're used
|>to atomically update files and such), so monitoring rename(2) wouldn't
|>be any help.
|
|
| Not to throw cold water on the notion of monitoring operations but to the
| extent that bzr aspires to control more than just text files maintained
| with simple Unix tools monitoring as I understand it is likely to find it
| "rough sledding".

| The MS Office Big 3 each
| follow a different paradigm to perform a reliable update.  These vary from
| MS Office release to release.  Here is what we found for the most recent
| release at that time (circa 2001):

This is pretty much what I was saying.

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

iD8DBQFCXqwn0F+nu1YWqI0RAhkKAJ4t4jdaotSx+oTt5W80lxvhVTZMsgCfQU63
WscJXV6BJPC4n3LnKIyH+g4=
=xttv
-----END PGP SIGNATURE-----