From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] APE inconsistencies
Date: Fri, 29 Mar 2013 15:20:01 -0700 [thread overview]
Message-ID: <4F539D6A-0B72-4D02-9266-C962735F2467@orthanc.ca> (raw)
In-Reply-To: <24472F85-7A42-4CDD-8CF2-5A1CEB25E109@corpus-callosum.com>
On 2013-03-29, at 11:26 AM, Jeff Sickel wrote:
> Not that BSD tries to be POSIX compliant
> any more or less than GNU/Linux.
FreeBSD is actually pretty good about adhering to POSIX/SUS/Xopen when you set the appropriate defines.
prev parent reply other threads:[~2013-03-29 22: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
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 [this message]
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=4F539D6A-0B72-4D02-9266-C962735F2467@orthanc.ca \
--to=lyndon@orthanc.ca \
--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).