Re: Loosing local changes during a commit

On Wed, 2004-03-17 at 11:58, Folker Schamel wrote:

> However, it seems that svn copies the file BACK from .svn/tmp/ into .
> Is this necessary, also if the file does not contain strings
> which must be replaced?

Ah, yes, good point. I had forgotten about this. This is required
whenever EOL or keyword translation is active. The algorithm is this:

  1. copy file to .svn/tmp/file, possibly "detranslating" in the process
(contracting keywords, and if svn:eol-style==native, converting to all
LF)

  2. commit .svn/tmp/file to repository.

  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.

> 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...?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 17 19:08:49 2004