Re: [rfc/remote] Tell remote stubs which signals are boring

Eli Zaretskii
2006-10-26T06:57:38Z

> Date: Wed, 25 Oct 2006 17:24:41 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> This is the solution I came up with for that problem, adjusted to HEAD
> and given a more sensible packet name. I have a tested implementation
> of this patch for HEAD, if my remote protocol choices are acceptable.
> The new mechanism is completely transparent to the user.

I'm confused: shouldn't this packet be automatically sent to a remote
target when I say, e.g., "handle SIGALRM nostop noprint pass"? Am I
missing something?