From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 4 May 2002 21:19:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 4 May 2002 21:18:59 -0400 Received: from adsl-63-194-239-202.dsl.lsan03.pacbell.net ([63.194.239.202]:15100 "EHLO mmp-linux.matchmail.com") by vger.kernel.org with ESMTP id ; Sat, 4 May 2002 21:18:58 -0400 Date: Sat, 4 May 2002 18:18:55 -0700 From: Mike Fedyk To: "M. Edward (Ed) Borasky" Cc: lkml Subject: Re: IO stats in /proc/partitions Message-ID: <20020505011855.GC2392@matchmail.com> Mail-Followup-To: "M. Edward (Ed) Borasky" , lkml In-Reply-To: <20020504213534.GA3034@louise.pinerecords.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, May 04, 2002 at 06:08:58PM -0700, M. Edward (Ed) Borasky wrote: > On Sat, 4 May 2002, Tomas Szepe wrote: > > > But hey, you've suffered thru it, which, guess what, makes you the > > perfect candidate to have the honor of writing the docs! > > The person who made the "design" decisions and implemented the code is > responsible for documenting it. At least that's what *I* was taught 40 > years ago when I learned to program a computer. True, but we don't know if the code designer is still around to do so either. By doing the code tracing yourself you are in a better position to submit informed documentation patches. This won't help the designer's habbits any, but it'll help others in the position that you were in before you did the tracing...