From: jbradford@dial.pipex.com
To: rddunlap@osdl.org (Randy.Dunlap)
Cc: jbm@joshisanerd.com, linux-kernel@vger.kernel.org
Subject: Re: Docs for 2.4.x -> 2.6.x
Date: Mon, 21 Oct 2002 17:17:15 +0100 (BST) [thread overview]
Message-ID: <200210211617.g9LGHFaO005410@darkstar.example.net> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0210210853370.29900-100000@dragon.pdx.osdl.net> from "Randy.Dunlap" at Oct 21, 2002 08:55:56 AM
> On Mon, 21 Oct 2002 jbradford@dial.pipex.com wrote:
>
> | > Would you volunteer to do the same thing for kernel API changes for those
> | > of us who don't pay enough attention to the list?
> |
> | Well, I'm certainly willing to spare the time to do it, but I'm not
> | sure that I'm particularly qualified to - the 2.4->2.6 doc would be
> | fairly straightforward for me, but documenting API changes in a useful
> | way may well require a better understanding of C than I have, (not
> | sure what I'd be letting myself in for - the only C I've done is
> | mainly games and other user mode stuff).
> |
> | > I have a few random drivers that aren't in mainline, so i always wind up
> | > porting to new kernels (they're trivial, so it's not a big deal, but
> | > sometimes it's annoying to find changes).
> | >
> | > Or is someone else already doing this wonderfully sexy job?
> |
> | It's possible they might be, I'm not sure...
> |
> | John.
> | -
>
> I got the impression that the first poster was asking
> for user-level 2.4 -> 2.6 migration HOWTO info,
> not kernel API changes. (such as "be sure that all of those
> CONFIG_INPU_options are enabled!")
Yes, that is really what I meant.
John.
prev parent reply other threads:[~2002-10-21 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 12:34 Docs for 2.4.x -> 2.6.x jbradford
2002-10-21 15:31 ` Josh Myer
2002-10-21 15:50 ` jbradford
2002-10-21 15:55 ` Randy.Dunlap
2002-10-21 16:17 ` jbradford [this message]
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=200210211617.g9LGHFaO005410@darkstar.example.net \
--to=jbradford@dial.pipex.com \
--cc=jbm@joshisanerd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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