From: Robert Marlow <bobstopper@australispro.com.au>
Cc: bug-guile@gnu.org
Subject: Re: Thread + Socket + Pipes Bug?
Date: 08 Aug 2003 09:09:31 +0800 [thread overview]
Message-ID: <1060304971.30311.2.camel@helicon> (raw)
In-Reply-To: <m3adalb1ni.fsf@laruns.ossau.uklinux.net>
Hi Neil
Sorry, I think I neglected to mention. I'm using Guile 1.6.4 on Solaris
and GNU/Linux.
Thanks heaps for checking it out.
On Fri, 2003-08-08 at 05:25, Neil Jerram wrote:
> Robert,
>
> You probably said in your earlier reports, but ... which version(s) of
> Guile do you see this bug with?
>
> (I'll try to make time over the weekend to investigate ...)
>
> Thanks,
> Neil
--
Regards,
Robert Marlow
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2003-08-08 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 7:58 Thread + Socket + Pipes Bug? Robert Marlow
[not found] ` <m3adalb1ni.fsf@laruns.ossau.uklinux.net>
2003-08-08 1:09 ` Robert Marlow [this message]
2003-08-10 21:19 ` Neil Jerram
2003-08-11 10:02 ` bobstopper
2003-08-12 23:06 ` Neil Jerram
2003-08-14 10:43 ` Robert Marlow
2003-08-15 22:35 ` Neil Jerram
2003-08-14 14:08 ` Robert Marlow
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=1060304971.30311.2.camel@helicon \
--to=bobstopper@australispro.com.au \
--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).