All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Weinehall <david@southpole.se>
To: "Markus Hästbacka" <midian@ihme.org>
Cc: Coywolf Qi Hunt <coywolf@lovecn.org>,
	Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [2.0.40-rc8] Works well
Date: Wed, 28 Jan 2004 16:17:27 +0100	[thread overview]
Message-ID: <20040128151727.GD16675@khan.acc.umu.se> (raw)
In-Reply-To: <Pine.LNX.4.44.0401280809470.20944-100000@midi>

On Wed, Jan 28, 2004 at 08:13:36AM +0200, Markus Hästbacka wrote:
> On Wed, 28 Jan 2004, David Weinehall wrote:
> 
> > On Wed, Jan 28, 2004 at 03:28:30AM +0000, Coywolf Qi Hunt wrote:
> > ...
> > > 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?
> >
> > Well, for sure it's quite a demanding task, since, if I remember
> > correctly, the module-code uses some nasty internal gcc-knowledge to
> > generate code, that simply doesn't work with later versions of gcc.
> > It might be that I remember this incorrectly though.
> >
> only the module-code? :)

Well, I do remember that I did spend a few weeks getting the 2.0-tree to
compile with gcc-3.2, and most problems arose when dealing with the
module-code.  I think I gave up there.

> > It would be interesting, yes, but only if it can be proved to some
> > degree that no new bugs are introduced.
> >
> That would probably be impossible to do without introducing any bugs..

Mmmm.

> > My aim for 2.0.41 is to make it a cleanup-release; remove warnings, tidy
> > up a little source-code mess, kill dead code, fix typos etc.
> >
> Sounds great, a bit amazing that 2.0 is alive again :)

Oh, it's not been dead, as much as laying dormant.


Regards: David
-- 
 /) David Weinehall <tao@acc.umu.se> /) Northern lights wander      (\
//  Maintainer of the v2.0 kernel   //  Dance across the winter sky //
\)  http://www.acc.umu.se/~tao/    (/   Full colour fire           (/

  reply	other threads:[~2004-01-28 15:17 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
2004-01-28  3:37       ` David Weinehall
2004-01-28  6:13         ` Markus Hästbacka
2004-01-28 15:17           ` David Weinehall [this message]
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=20040128151727.GD16675@khan.acc.umu.se \
    --to=david@southpole.se \
    --cc=coywolf@lovecn.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=midian@ihme.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.