From: Amirouche Boubekki <amirouche@hypermove.net>
To: 23000@debbugs.gnu.org
Subject: bug#23000: update from wingo
Date: Tue, 03 May 2016 11:07:58 +0200 [thread overview]
Message-ID: <26d9fb7cad72c6a91ad20a57e1651313@hypermove.net> (raw)
In-Reply-To: <0c47cb865118629de2217d50490346d0@hypermove.net>
wingo said:
> wingo | i don't think that's a guile bug -- i think in that case you
> need to handle SIGPIPE
> wingo | b/c posix is weird
> wingo | (sigaction SIGPIPE SIG_IGN)
> wingo | the web server does it.
next prev parent reply other threads:[~2016-05-03 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 18:57 bug#23000: send doesn't check for closed socket Amirouche Boubekki
2016-05-03 9:07 ` Amirouche Boubekki [this message]
2016-06-20 16:18 ` bug#23000: update from wingo Andy Wingo
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=26d9fb7cad72c6a91ad20a57e1651313@hypermove.net \
--to=amirouche@hypermove.net \
--cc=23000@debbugs.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).