From: ludo@gnu.org (Ludovic Courtès)
To: "Andy Wingo" <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Signal thread
Date: Mon, 27 Jun 2011 18:00:14 +0200 [thread overview]
Message-ID: <87boxjuuwh.fsf@gnu.org> (raw)
In-Reply-To: <E1QZiQ3-0008H5-HJ@vcs-noshell.in.savannah.gnu.org> (Andy Wingo's message of "Thu, 23 Jun 2011 11:49:59 +0000")
Hello!
"Andy Wingo" <wingo@pobox.com> skribis:
> commit 3b971a59b55586a236c3621a55515d9272ee5c80
> Author: Andy Wingo <wingo@pobox.com>
> Date: Thu Jun 23 11:24:16 2011 +0200
>
> don't spawn the signal delivery thread in a thread-exit handler
>
> * libguile/threads.c (do_thread_exit): Remove needless spawn of the
> signal delivery thread.
Out of curiosity, what’s the rationale? Should it be done in stable-2.0
as well?
As a side note, why does this area have to change so often? :-)
Thanks,
Ludo’.
next parent reply other threads:[~2011-06-27 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1QZiQ3-0008H5-HJ@vcs-noshell.in.savannah.gnu.org>
2011-06-27 16:00 ` Ludovic Courtès [this message]
2011-06-27 20:44 ` Signal thread Andy Wingo
2011-06-28 16:46 ` Ludovic Courtès
2011-06-28 19:52 ` Andy Wingo
2011-06-29 15:51 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87boxjuuwh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).