Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 21 Dec 2001 11:50:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 21 Dec 2001 11:50:30 -0500 Received: from air-1.osdl.org ([65.201.151.5]:23050 "EHLO osdlab.pdx.osdl.net") by vger.kernel.org with ESMTP id ; Fri, 21 Dec 2001 11:50:19 -0500 Date: Fri, 21 Dec 2001 08:47:04 -0800 (PST) From: "Randy.Dunlap" X-X-Sender: To: Andreas Bombe cc: Subject: Re: 2.5.1 API change summary In-Reply-To: <20011221030218.GA3893@storm.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 21 Dec 2001, Andreas Bombe wrote: | On Tue, Dec 18, 2001 at 11:28:02AM -0800, Randy.Dunlap wrote: | > On Tue, 18 Dec 2001, Andreas Bombe wrote: | > | > http://www.osdl.org/archive/rddunlap/linux-port-25x.html . | | Nice. I wasn't aware of that page. So basically you attack the same | problem I do (that it's not obvious that a thread on linux-kernel or | other lists have interesting information deeply embedded). You point to Right. and most people don't want to dig for the info. :) | the archived discussions and documentation whereas I just want to list | the changes that did actually make it into a certain revision, without | documenting much. Your method catches more of the detailed changes -- I had missed a few. Mine captures discussion and decision-making. Both have merits and are useful. | We could probably combine our efforts, but I can't think of a way how | (apart from just pointing to each other). I've updated mine to do that. It will appear soon. Thanks, -- ~Randy - 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/