> The latter is not the same as 'svn up', but rather
>
> $ svn up -N file-1
> ...
> ...
> $ svn up -N dir-N/file-M
>
> Which sleeps for 1 second after every 'svn up' call. It's called
> "sleeping for timestamps". We do it so that we know that the clock has
> advanced enough for any script modifying the working copy will
> actually advance the last-modified time on the modified file (on Unix,
> many filesystems have a 1s timestamp resolution).
>
> I hope the above explains it...
It goes a long way in explaining it the mechanics of the problem, but
maybe not the reason for implementing it that way.
Why is a single invocation of:
svn up file1 file2 file3
the same as:
svn up file1
svn up file2
svn up file3
?
There can be no script running between updates in the first, thus no
reason for "sleeping for timestamps" (post-update hook scripts should
obviously get the entire update list instead of one-by-one).
Why can't the client marshal the update targets in a single action -
bypassing the recursive crawl of standard update, or seeding it with
several recursion roots?
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 23 23:54:50 2007