Re: Make output from hooks visible

> Why are they waiting for the hook to execute? That sounds like a
> terrible thing to do to users. Why isn't the hook being launched with
> a '&' so it can run in the background?

Because the hook may determine that the changeset should not be
commited. For example, the hook may determine that the SCM user is
trying to apply a changeset to a bug that has already been closed.
In general, a number of integration policies could apply logic that
confirms the check-in should be allowed. Examples of those verification
checks (performed by Scmbug) are at:

http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-10-0/manual/html/x194.html

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 29 20:13:32 2006