Re: Loosing local changes during a commit

Ben Collins-Sussman wrote:

> ...
>
> 3. copy .svn/tmp/file to ./file, "retranslating" to native EOL style
> and re-expanding keywords with new values.
>
>
> If you don't have any eol- or keyword-translation active, then step 3
> never happens.

Ahhh, I see!
The file has EOL-style it set, yes!

>>Subversion seems to be protected by complicated locking mechanisms
>>against another svn instance accessing the wc data in parallel;
>>but it seems to be not protected against any other app accessing the
>>wc data in parallel
>
>
> That is a true observation. As you suggested, perhaps setting the
> working-file to read-only during the commit might be enough...?

Would be fine for example.

It is no serious problem. You are right, I tried to be too clever,
effectively doing "something bad".

A trivial thing would be to add a warning to the svn book,
mention that you should not change the file while comitting.

Setting to read-only would be a nice thing!

Cheers,
Folker

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 17 20:18:29 2004