> > This is actually incorrect. Danny's issues were due to > > misconfiguration, not code errors. There was one errant notify(), but > > it did not cause the problem Danny observed. > > This is not what Danny said in his last mail on testing. Did he retest ?
Woah, hey.. I'll test patches, but I'm *not* going to re-configure by myself to make them work, in case the effore I put in biases me to one or other solution. If a patch nees a certain configuration to perform correctly, patch config as well. And guys.. frankly, why the hell can't we have a watchdog replacement for the scheduler , and leave out the refactoring? d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
