From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org
Subject: Re: [bug #29574] VM stack overflows aren't properly handled [1.9.10]
Date: Sat, 22 May 2010 17:55:09 +0200 [thread overview]
Message-ID: <87r5l4szhe.fsf@gnu.org> (raw)
In-Reply-To: <m3bpc8xaoe.fsf@pobox.com> (Andy Wingo's message of "Sat, 22 May 2010 16:39:45 +0200")
Hey,
Andy Wingo <wingo@pobox.com> writes:
> On Sat 22 May 2010 11:34, ludo@gnu.org (Ludovic Courtès) writes:
>
>> Please reply through the bug tracker
>> <http://savannah.gnu.org/bugs/?29574>. The patch is there.
>
> I never doubted the presence of the patch, I was only a bit miffed as I
> work best offline.
Oh right.
> Perhaps this should form part of our ongoing conversations with
> Sylvain ;)
Definitely! :-)
Ludo’.
next prev parent reply other threads:[~2010-05-22 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 9:01 [bug #29574] VM stack overflows aren't properly handled [1.9.10] Ludovic Courtès
2010-05-11 21:33 ` Ludovic Courtès
2010-05-21 11:27 ` Andy Wingo
2010-05-22 9:34 ` Ludovic Courtès
2010-05-22 14:39 ` Andy Wingo
2010-05-22 15:55 ` Ludovic Courtès [this message]
2010-05-24 14:51 ` Ken Raeburn
2010-05-26 21:56 ` 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=87r5l4szhe.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guile@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).