Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 21 Oct 2002 11:35:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 21 Oct 2002 11:35:49 -0400 Received: from 62-190-200-233.pdu.pipex.net ([62.190.200.233]:268 "EHLO darkstar.example.net") by vger.kernel.org with ESMTP id ; Mon, 21 Oct 2002 11:35:48 -0400 From: jbradford@dial.pipex.com Message-Id: <200210211550.g9LFoh1u005234@darkstar.example.net> Subject: Re: Docs for 2.4.x -> 2.6.x To: jbm@joshisanerd.com (Josh Myer) Date: Mon, 21 Oct 2002 16:50:43 +0100 (BST) Cc: linux-kernel@vger.kernel.org In-Reply-To: from "Josh Myer" at Oct 21, 2002 10:31:37 AM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1062 Lines: 24 > 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/