From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] u.h & ape
Date: Fri, 11 Jan 2013 14:56:32 -0600 [thread overview]
Message-ID: <C14878CF-F8A8-4AC6-A374-23F47DFCC4F3@corpus-callosum.com> (raw)
Can someone enlighten me about the history of /$objtype/include/u.h and why APE chose to do /sys/include/ape/u.h? There are a few cases where getting specific Plan 9 libraries massaged enough to be used from APE source gets to be a little more awkward because u.h is not architecture independent.
-jas
next reply other threads:[~2013-01-11 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 20:56 Jeff Sickel [this message]
2013-01-11 22:06 ` Steve Simon
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=C14878CF-F8A8-4AC6-A374-23F47DFCC4F3@corpus-callosum.com \
--to=jas@corpus-callosum.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).