From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: Re[3]: [9fans] hehe bad to worse
Date: Thu, 10 May 2001 18:37:56 +0100 [thread overview]
Message-ID: <20010510174119.5F3CE199F9@mail.cse.psu.edu> (raw)
>>in /sys/src/9/pc/mkfile, ensure you've got:
>> pgrp.$O\
>> portclock.$O\
>> print.$O\
although true, ignore that: i misread the diagnostic as undefined not redefinition.
presotto's comment is correct.
next reply other threads:[~2001-05-10 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 17:37 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-10 17:28 presotto
2001-05-10 17:28 forsyth
2001-05-10 16:27 Re[2]: " presotto
2001-05-10 16:57 ` Re[3]: " Matt H
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=20010510174119.5F3CE199F9@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--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).