From: Keith Owens <kaos@ocs.com.au>
To: "J . A . Magallon" <jamagallon@able.es>
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, 01 May 2001 09:46:39 +1000 [thread overview]
Message-ID: <16913.988674399@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Tue, 01 May 2001 01:31:20 +0200." <20010501013120.A15120@werewolf.able.es>
On Tue, 1 May 2001 01:31:20 +0200,
"J . A . Magallon" <jamagallon@able.es> wrote:
>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
>
>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.
But 2.4 kbuild for multi part objects already works, there is no bug to
fix or live with. 2.4 is supposed to be bug fixes only. IMHO keeping
the existing boilerplate method for multi part objects in 2.4 is the
safer approach, don't rock the boat.
next prev parent reply other threads:[~2001-04-30 23:47 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
2001-04-30 23:46 ` Keith Owens [this message]
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=16913.988674399@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=jamagallon@able.es \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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