From: Coywolf Qi Hunt <coywolf@lovecn.org>
To: "Markus Hästbacka" <midian@ihme.org>
Cc: David Weinehall <tao@debian.org>,
Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [2.0.40-rc8] Works well
Date: Wed, 28 Jan 2004 03:28:30 +0000 [thread overview]
Message-ID: <40172C5E.3090201@lovecn.org> (raw)
In-Reply-To: <1075223456.5219.1.camel@midux>
Markus Hästbacka wrote:
>Hey David,
>I just mail to tell you that 2.0.40-rc8 seems to work really well, no
>problems compiling (except a few warnings :) and absolutely no problem
>running. Great work!
>
> Markus
>
>
Hello all 2.0 hackers,
Recently I just have such an idea that is to port the 2.0.39 to let it
be compiled with my gcc 2.95.4 or any
other latest gcc. At the same time, also make it remain compliant to
gcc 2.7.2.1. ( I can't find 2.7.2.1, only 2.7.2.3
on the ftp) Is this work worth while?
Coywolf
next prev parent reply other threads:[~2004-01-28 3:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 19:23 [PATCH 2.0.39] put_last_free() defined, but not used Coywolf Qi Hunt
2004-01-25 22:29 ` David Weinehall
2004-01-25 23:43 ` Jens Axboe
2004-01-26 2:01 ` David Weinehall
2004-01-27 17:10 ` [2.0.40-rc8] Works well Markus Hästbacka
2004-01-27 17:38 ` David Weinehall
2004-01-28 3:28 ` Coywolf Qi Hunt [this message]
2004-01-28 3:37 ` David Weinehall
2004-01-28 6:13 ` Markus Hästbacka
2004-01-28 15:17 ` David Weinehall
2004-01-28 23:37 ` Markus Hästbacka
2004-01-28 23:50 ` David Weinehall
2004-02-23 6:28 ` about 2.0 cleanup or adaption Coywolf Qi Hunt
2004-03-03 13:38 ` [PATCH 2.0.40] Fix comment error of prepare_binprm() in exec.c Coywolf Qi Hunt
2004-03-03 13:51 ` David Weinehall
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=40172C5E.3090201@lovecn.org \
--to=coywolf@lovecn.org \
--cc=linux-kernel@vger.kernel.org \
--cc=midian@ihme.org \
--cc=tao@debian.org \
/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