Re: Serious incompatibility between Subversion and Metrowerks CodeWarrior

On Aug 1, 2005, at 1:17 PM, Ben Collins-Sussman wrote:

> I've never heard of an editor which didn't notice that a file's
> inode (or contents) had changed. That sounds like a serious bug in
> the editor.

Yes, well, one might argue that it's a shortcoming of an editor, but
hardly a bug to notice that a file's inode has changed. I mean, it's
got an open file handle, it shouldn't expect the file to be deleted.
However, why a subsequent save doesn't at least report an error, I
don't know. That's definitely a bug, and would be enough to prevent
me, generally from losing work.

It's also a shortcoming, but not a bug, that it doesn't notice the
file contents have changed. Handling such a change is non-trivial
(what to do with the change? what do do with unsaved changes in the
buffer? etc.). However, this is not really the problem, as it's the
file being deleted that causes trouble.

Is there any reason why subversion couldn't just write the new
contents to the old file? (I suppose this is really a question for
the dev list.)

-- 
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org