From: Keith Owens <kaos@ocs.com.au>
To: Frank Davis <fdavis@andrew.cmu.edu>
Cc: Sven Vermeulen <sven.vermeulen@rug.ac.be>,
PENG Zhaowang <pangzw@263.net>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.7 build failure : esssolo1.c troubles
Date: Sun, 22 Jul 2001 01:12:55 +1000 [thread overview]
Message-ID: <21507.995728375@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 21 Jul 2001 11:07:31 -0400." <Pine.GSO.4.21L-021.0107211102200.1910-100000@unix14.andrew.cmu.edu>
On Sat, 21 Jul 2001 11:07:31 -0400 (EDT),
Frank Davis <fdavis@andrew.cmu.edu> wrote:
> I'm sure Keith and others fixed this problem a while ago through
>fixing the config options...
It was fixed in the -ac patches.
next prev parent reply other threads:[~2001-07-21 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-21 15:07 Re:2.4.7 build failure : esssolo1.c troubles Frank Davis
2001-07-21 15:12 ` Keith Owens [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-21 12:25 2.4.7 " Sven Vermeulen
2001-07-21 12:47 ` Alexander Griesser
2001-07-21 14:56 ` Sven Vermeulen
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=21507.995728375@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=fdavis@andrew.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pangzw@263.net \
--cc=sven.vermeulen@rug.ac.be \
/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