On Feb 12, 2008, at 11:58 AM, Michael Weaver wrote:
> When I run the svn lock command, example below, my hook runs 3x and
> I get 3 emails one listing with each path below on stdin. Shouldn’t
> I be getting a list of files on stdin with the hook being called
> once, with one email? Has anyone ever seen this? I am running
> subversion 1.4.5. I think according to the documentation everything
> after 1.3 should pass a list into stdin of the hook?
>
> C:\Documents and Settings\MWeaver.viewpoint\Desktop\Test>svn lock
> "test folder\n
> ew text document (6).txt" "test folder\new text document.txt" "test
> folder\new t
> ext document (5).txt" -m ""
> 'New Text Document (5).txt' locked by user 'mjw'.
> 'New Text Document (6).txt' locked by user 'mjw'.
> 'New Text Document.txt' locked by user 'mjw'.
>
> Thanks,
>
> Mike
We found a similar behavior with 'svn update'. As it turns out, the
svn client will create a separate repository access session for each
individual file target given on the command-line. For example:
% svn update file1 file2 file3 file4*
The wildcard expands into an even bigger list of files. We use svn
+ssh as our access method and found that it would open a new SSH
session for each individual target given. This also happens if you
directly use the SWIG wrappers. When you attempt to update a large
number of individual targets you get a huge overhead from each of the
individual connections.
Anyhow back to your problem - I would guess it would be very difficult
to make this command look like a single operation on the server end,
since it is the client that is producing multiple 'lock' operations.
-Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-12 21:48:27 CET