From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] APE inconsistencies
Date: Fri, 29 Mar 2013 17:20:05 +0000 [thread overview]
Message-ID: <CAOw7k5jkDwG4fant7hJNPk_1ivDLJhAaZiH72xAid=6mq9Tgxg@mail.gmail.com> (raw)
In-Reply-To: <17666A31-B506-46C1-972F-2D6407C4B8DD@corpus-callosum.com>
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
On 29 March 2013 17:13, Jeff Sickel <jas@corpus-callosum.com> wrote:
> Does anyone know if the netdb.h inclusion of hstrerror(int) was
> just a copy/paste error? Of if hstrerror() was intended to be
> in the ape/lib/bsd source but got dropped somehow?
>
the linux manual page describes hstrerror as obsolete
[-- Attachment #2: Type: text/html, Size: 634 bytes --]
next prev parent reply other threads:[~2013-03-29 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 17:13 Jeff Sickel
2013-03-29 17:20 ` Charles Forsyth [this message]
2013-03-29 17:25 ` Jeff Sickel
2013-03-29 17:41 ` Kurt H Maier
2013-03-29 18:00 ` Charles Forsyth
2013-03-29 18:26 ` Jeff Sickel
2013-03-29 19:03 ` tlaronde
2013-03-29 19:12 ` Kurt H Maier
2013-03-29 20:10 ` tlaronde
2013-03-29 20:32 ` Charles Forsyth
2013-03-30 2:37 ` a
2013-03-29 22:20 ` Lyndon Nerenberg
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOw7k5jkDwG4fant7hJNPk_1ivDLJhAaZiH72xAid=6mq9Tgxg@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).