From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: generic async event handlers in the event loop, for remote non-stop (was: generic `struct serial' interface pipe for remote non-stop)
Date: Fri, 24 Oct 2008 16:40:00 -0000 [thread overview]
Message-ID: <ur666x7zf.fsf@gnu.org> (raw)
In-Reply-To: <200810241512.55053.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Fri, 24 Oct 2008 15:12:54 +0100
>
> On Friday 24 October 2008 10:54:36, Eli Zaretskii wrote:
> > > From: Pedro Alves <pedro@codesourcery.com>
> > > Date: Fri, 24 Oct 2008 01:32:41 +0100
> > >
> > > signal handlers should keep the current behaviour of having high
> > > priority in relation to normal events
> >
> > I don't necessarily disagree, but can you explain why is that?
>
> Sure! But, do you see a case to change that established behaviour?
No, not after your explanation (mostly that they are already
delayed at that point).
Thanks.
next prev parent reply other threads:[~2008-10-24 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 0:33 Pedro Alves
2008-10-24 9:56 ` Eli Zaretskii
2008-10-24 14:14 ` Pedro Alves
2008-10-24 16:40 ` Eli Zaretskii [this message]
2008-10-24 19:37 ` Pedro Alves
2008-10-24 19:41 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ur666x7zf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox