From: "Mark Chambers" <markc@mail.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: "Embedded Linux PPC list" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 2.4 versus 2.6 patches
Date: Mon, 26 Jul 2004 11:08:44 -0400 [thread overview]
Message-ID: <00ab01c47322$73784280$0301a8c0@chuck2> (raw)
In-Reply-To: Pine.LNX.4.58.0407261021120.6190@localhost.localdomain
> If 2.4 works already for you, by all means use it -- but if you're doing
> any new development, or you _really_ want people to care when you find
> bugs, it really ought to be 2.6.
>
Well, this is a surprise to me. Does the stock 2.6 even compile on 8xx yet,
or are you talking about 8xxx and/or IBM?
Mark Chambers
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-26 15:08 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
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 [this message]
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='00ab01c47322$73784280$0301a8c0@chuck2' \
--to=markc@mail.com \
--cc=dwmw2@infradead.org \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).