From: "J . A . Magallon" <jamagallon@able.es>
To: Keith Owens <kaos@ocs.com.au>
Cc: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] [PATCH] automatic multi-part link rules (fwd)
Date: Tue, 1 May 2001 01:31:20 +0200 [thread overview]
Message-ID: <20010501013120.A15120@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.4.33.0105010022020.24511-100000@vaio> <16302.988670989@ocs3.ocs-net>
In-Reply-To: <16302.988670989@ocs3.ocs-net>; from kaos@ocs.com.au on Tue, May 01, 2001 at 00:49:49 +0200
On 05.01 Keith Owens wrote:
>
> The patch appears to work but is it worth applying now? The existing
> 2.4 rules work fine and the entire kbuild system will be rewritten for
> 2.5, including the case you identified here. It struck me as a decent
> change but for no benefit and, given that the 2.4 kbuild system is so
> fragile, why not live with something we know works until 2.5 is
> available?
>
We will have to live with 2.4 until 2.6, 'cause 2.5 will not be stable.
2.4 will be the stable and non "brain damaged" kernel in distros.
So every thing that can make 2.4 more clean, better. Think in 2.4.57,
and we still are in 4. And feature backports, and new drivers...
The 2.5 rewrite is not excuse. The knowledge on the actual state, yes.
--
J.A. Magallon # Let the source
mailto:jamagallon@able.es # be with you, Luke...
Linux werewolf 2.4.4 #1 SMP Sat Apr 28 11:45:02 CEST 2001 i686
next prev parent reply other threads:[~2001-04-30 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 22:43 [PATCH] automatic multi-part link rules (fwd) Kai Germaschewski
2001-04-30 22:49 ` [kbuild-devel] " Keith Owens
2001-04-30 23:31 ` J . A . Magallon [this message]
2001-04-30 23:46 ` Keith Owens
2001-05-01 8:16 ` Kai Germaschewski
2001-05-01 17:23 ` Peter Samuelson
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=20010501013120.A15120@werewolf.able.es \
--to=jamagallon@able.es \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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