On Aug 1, 2005, at 3:27 PM, Rick Mann wrote:
>
> 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.
Yeah, that's what I meant. In something like emacs, you get the
error as soon as you try to save: "file changed on disk! are you
sure you want to save??"
>
> 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.)
Yes, writing directly to the file wouldn't be an atomic change.
Moving a new file on top is atomic.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 1 22:44:46 2005