From: Kris Maglione <bsdaemon@comcast.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Page ported to plan9port
Date: Fri, 9 Feb 2007 13:09:53 -0500 [thread overview]
Message-ID: <20070209180953.GC53966@fw.home> (raw)
In-Reply-To: <ee9e417a0702090952n147cf24ev77b6ec4af1ba7c47@mail.gmail.com>
On Fri, Feb 09, 2007 at 12:52:14PM -0500, Russ Cox wrote:
>I'd be happy to send it to them for inclusion if
>someone else would confirm that it compiles
>against the latest gs sources.
Yes, it does, against AFPL, at least. Uriel tried it with GNU and I seem
to recall that it compiled, but he got fed up with the build system.
next prev parent reply other threads:[~2007-02-09 18:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 23:10 Kris Maglione
2007-02-08 23:29 ` erik quanstrom
2007-02-09 2:58 ` Russ Cox
2007-02-09 9:24 ` Charles Forsyth
2007-02-09 16:44 ` Kris Maglione
2007-02-09 17:21 ` Russ Cox
2007-02-09 17:32 ` Kris Maglione
2007-02-09 17:52 ` Russ Cox
2007-02-09 18:09 ` Kris Maglione [this message]
2007-03-26 20:57 ` Russ Cox
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=20070209180953.GC53966@fw.home \
--to=bsdaemon@comcast.net \
--cc=9fans@cse.psu.edu \
/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).