post-commit hook - correct behaviour to client

hi

i have noticed this behavior, which seems odd to me. can anyone verify
that this scenario is indeed correct ?

* user commits a change via commandline or tortoiseSVN

    $ svn ci -m "" file
    Sending file
    Transmitting file data ....

* post-commit (a batch file on windows 2003) invokes a perl script
* perl script sleeps say 120 seconds
* meanwhile user verifies that file is indeed committed via repository
browsing and notes the latest revision to be 434

(120 seconds pass)

* client outputs:

   Committed revision 434.

i don't understand why the client have to wait for a response from a
post-commit when it is already committed and when one cannot even return
an exit code for the client to use.

./allan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 20 20:52:30 2005