From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Re: [PATCH]: deadlock in make_struct()
Date: Sun, 30 Nov 2008 20:34:25 +0100 [thread overview]
Message-ID: <87tz9povni.fsf@gnu.org> (raw)
In-Reply-To: 49dd78620811191452y1b6fe1eegfacf0407aef040db@mail.gmail.com
Hello!
"Neil Jerram" <neiljerram@googlemail.com> writes:
> 2008/11/18 Ludovic Courtès <ludo@gnu.org>:
>
>>
>> Kevin asked the same question a while back:
>>
>> http://lists.gnu.org/archive/html/guile-devel/2007-02/msg00006.html
>>
>> One we've had enough developers wondering why it's here, maybe we can
>> safely remove it. :-)
>
> I agree. I also can't see any reason for the critical section, so
> would be happy to commit Linas's patch.
I just committed it, after re-reaching the conclusion that there's no
reason to have a critical section here AFAICS.
Thanks,
Ludo'.
next prev parent reply other threads:[~2008-11-30 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 18:28 [PATCH]: deadlock in make_struct() Linas Vepstas
2008-11-17 21:41 ` Andy Wingo
2008-11-18 13:34 ` Ludovic Courtès
2008-11-19 22:52 ` Neil Jerram
2008-11-30 19:34 ` Ludovic Courtès [this message]
2008-11-18 22:05 ` Linas Vepstas
2008-11-19 12:21 ` Han-Wen Nienhuys
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=87tz9povni.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guile@gnu.org \
/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).