Read-only status caching

[Michael Kujawa]

It seems like Cirrus caches the Read-only attribute of a file during a 2-way comparison, and doesn't update it unless Cirrus loses focus. I happened to be comparing across machines, and checked the file out on the remote machine. Cirrus didn't recognize this when I went to save.

Suggestion: Have cirrus refresh the file's status when I tell it to save, before prompting to overwrite.

[Tim]

We should be able to get this fixed for the next release.