From: "Benjamin Huntsman" <BHuntsman@mail2.cu-portland.edu>
To: "Russ Cox" <russcox@gmail.com>,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: RE: [9fans] http://swtch.com/plan9port/mk-all-20040301.tgz
Date: Thu, 13 Jan 2005 22:55:13 -0800 [thread overview]
Message-ID: <7DD37218104E31429E79EB0BB136800E11C55A@vargas.ntdom.cupdx> (raw)
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
so what's more current these days- plan9port or actual Plan 9? Last I heard, plan9port's Venti was more functional than the real Plan 9 variety...
-Ben
-----Original Message-----
From: Russ Cox [mailto:russcox@gmail.com]
Sent: Thu 1/13/2005 6:15 PM
To: Fans of the OS Plan 9 from Bell Labs
Cc:
Subject: Re: [9fans] http://swtch.com/plan9port/mk-all-20040301.tgz
thanks.
On Thu, 25 Nov 2004 23:46:13 +0100, boyd, rounin <boyd@insultant.net> wrote:
> the Makefile is just bust. this is what it should look like:
>
> all:
> for i in libutf libfmt libbio libregexp mk ; \
> do \
> (cd $$i; make) ; \
> done
> ls -l mk/mk
>
> --
> MGRS 31U DQ 52572 12604
>
>
[-- Attachment #2.1: Type: text/plain, Size: 292 bytes --]
from postmaster@ethel:
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Type: application/ms-tnef;
name="winmail.dat"
Content-Transfer-Encoding: base64
[-- Attachment #2.2: winmail.dat.suspect --]
[-- Type: application/octet-stream, Size: 4622 bytes --]
next reply other threads:[~2005-01-14 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 6:55 Benjamin Huntsman [this message]
2005-01-14 17:03 ` Ronald G. Minnich
-- strict thread matches above, loose matches on Subject: below --
2004-11-25 22:46 boyd, rounin
2005-01-14 2:15 ` 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=7DD37218104E31429E79EB0BB136800E11C55A@vargas.ntdom.cupdx \
--to=bhuntsman@mail2.cu-portland.edu \
--cc=9fans@cse.psu.edu \
--cc=russcox@gmail.com \
/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).