Re: Make output from hooks visible

"Ben Collins-Sussman" <sussman@red-bean.com> writes:

> On 3/29/06, Kristis Makris <kristis.makris@asu.edu> wrote:
>>
>> > Alternatively we don't agree with your assessment of the bug.
>>
>> Could I ask why ?

Different people might have different reasons. Perhaps nobody has
explained the exact problem. Perhaps nobody has put forward a
convincing argument as to why it is necessary. Or perhaps the
implementation costs outweigh the benefits.

>> If one is importing 4000 files, and they have to wait for the hooks to
>> execute, they have no idea if Subversion deadlocked or whether the hook
>> is really executing (or access to the bugtracker for integration is
>> commencing).
>
> 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?

That sounds like you assume Kristis Makris is talking about
post-commit output, but I'm not so sure. It could be a request to
make a hooks stdout output get back to the client. Or it could be a
request to make a hooks stderr output get back to the client even when
the hook succeeds. It could even be a request that the hooks output
should get back to the client while the hook is running.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org