Re: Files changed on svn update

Ben Collins-Sussman <sussman@collab.net> writes:

> You're saying that an .svn/entries file's timestamp is touched even when
> the *entire* directory is already at HEAD? I wonder if that's just part
> of our locking code. When libsvn_wc's update process "opens" a working
> copy dir, it 'locks' it and reads the entries file into memory, possibly
> tweaking stuff. When the directory is closed, the entries file is
> written back to disk and the lockfile removed. I wonder if this code is
> being overzealous and writing the entries file unconditionally?

I suspect it is the "incomplete" flag. If I'm right the entries file
first gets written with "incomplete=true" and later gets written
without the flag. I suppose it might be possible to delay writing the
incomplete flag--perhaps by using a flag in the access baton and
writing the incomplete flag the first time some other change is made.
Then it should be possible to avoid writing the entries file at all if
no changes are made. A minor complication is that the code needs to
handle the case where the entries file starts out incomplete but no
changes need to be made.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org