public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jbradford@dial.pipex.com
To: jbm@joshisanerd.com (Josh Myer)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Docs for 2.4.x -> 2.6.x
Date: Mon, 21 Oct 2002 16:50:43 +0100 (BST)	[thread overview]
Message-ID: <200210211550.g9LFoh1u005234@darkstar.example.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0210211028340.1066-100000@blessed> from "Josh Myer" at Oct 21, 2002 10:31:37 AM

> 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.

  reply	other threads:[~2002-10-21 15:35 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 [this message]
2002-10-21 15:55     ` Randy.Dunlap
2002-10-21 16:17       ` jbradford

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=200210211550.g9LFoh1u005234@darkstar.example.net \
    --to=jbradford@dial.pipex.com \
    --cc=jbm@joshisanerd.com \
    --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