From: David Woodhouse <dwmw2@infradead.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 2.4 versus 2.6 patches
Date: Sat, 24 Jul 2004 11:20:08 -0400 [thread overview]
Message-ID: <1090682408.4195.3.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.60.0407231055450.5463@localhost.localdomain>
On Fri, 2004-07-23 at 10:57 -0400, Robert P. J. Day wrote:
> for most of the folks on this list, i suspect they'd be more
> interested in patches to a 2.6-style Kconfig file, not a 2.4-style
> config.in file, correct?
Yes. The 2.4 kernel is dead.
There are two classes of people -- those who are shipping 2.4 already or
at least close to doing so, and those who are bringing Linux up on a new
board.
The former are hopefully already past the stage of being confused by
such things in the config files, and the latter should most definitely
be using 2.6.
--
dwmw2
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-24 15:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 14:57 2.4 versus 2.6 patches Robert P. J. Day
2004-07-24 15:20 ` David Woodhouse [this message]
2004-07-26 2:50 ` Song Sam
2004-07-26 4:13 ` David Woodhouse
2004-07-26 4:40 ` Eugene Surovegin
2004-07-26 13:48 ` Song Sam
2004-07-26 14:27 ` David Woodhouse
2004-07-26 15:08 ` Mark Chambers
2004-07-26 15:53 ` Robert P. J. Day
2004-07-26 16:30 ` Eugene Surovegin
2004-07-26 23:17 ` Thomas Gleixner
2004-07-26 23:49 ` Eugene Surovegin
2004-07-27 0:25 ` Thomas Gleixner
2004-07-29 19:30 ` David Woodhouse
2004-07-26 17:16 ` Wolfgang Denk
2004-08-09 15:03 ` Marcelo Tosatti
2004-07-27 3:13 ` Song Sam
2004-08-09 13:28 ` Marcelo Tosatti
2004-08-10 5:58 ` Song Sam
2004-08-10 11:54 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2004-07-26 16:48 Demke, Torsten
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=1090682408.4195.3.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rpjday@mindspring.com \
/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.