Folks,
I have implemented the 0.12 post-commit repo hook for our windows/apache
based subversion server to update associated trac tickets. However, it
seems to significantly increase the commit time (23 seconds for a
single, simple VB class file that used to take a few seconds).
So I am considering changing the recommended windows .cmd file from:
{{{
@C:\Python26\Scripts\trac-admin.exe <env-dir> changeset added "%1" "%2"
}}}
...to...
{{{
@start C:\Python26\Scripts\trac-admin.exe <env-dir> changeset added "%1"
"%2"
}}}
...which I believe should not wait for the spawned program to complete
before continuing (and therefore returning).
Are there any obvious flaws with this plan that I have missed? I know I
will not get any text that trac-admin might send to stderr but then we
don't return an exit code (from the .cmd hook) so I don't think that
would happen anyway?
Many thanks,
~ Mark C
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en.
