From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] devarch.c mb build errors
Date: Mon, 15 Dec 2003 19:06:35 +0000 [thread overview]
Message-ID: <3644993faf57f2cdcd7a20586cda5acf@caldo.demon.co.uk> (raw)
In-Reply-To: <3FDE03D4.9080902@cox.net>
>>Any insight as to why this is happening, and or a possible [way to] fix?
some new/renamed functions haven't turned up yet.
l.s i'd have thought, but we'll see.
the fix from your point of view is probably to mention it here, then wait.
prev parent reply other threads:[~2003-12-15 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 18:56 Chris Van Horne
2003-12-15 19:01 ` jmk
2003-12-15 19:06 ` Charles Forsyth [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=3644993faf57f2cdcd7a20586cda5acf@caldo.demon.co.uk \
--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).