mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: vda@port.imtp.ilyichevsk.odessa.ua, info@global-digicom.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: White Paper on the Linux kernel VM?
Date: Thu, 24 Jan 2002 19:21:19 +0100	[thread overview]
Message-ID: <E16ToWW-0002mj-00@starship.berlin> (raw)
In-Reply-To: <20020124033618.20653.cpmta@c001.snv.cp.net> <200201241206.g0OC66E10502@Port.imtp.ilyichevsk.odessa.ua>
In-Reply-To: <200201241206.g0OC66E10502@Port.imtp.ilyichevsk.odessa.ua>

On January 24, 2002 05:06 pm, Denis Vlasenko wrote:
> Writing docs wastes developer's time: they will write how they want VM to 
> operate or how they think it operates (while some bug can make actual VM 
> operate differently) instead of improving/debugging current VM code.

No you're wrong.  Not writing docs wastes the time of other developers.  It 
sends the message 'my time is more important than yours'.  In the case of 
Linus, that may be true, but it's very definitely not true for any other core 
developer.

It is the responsibility of each developer to prepare at least minimal - but 
sufficient - documentation for the work they do.  Others who specialize in 
preparing documentation can then use that material as a starting point for 
preparing clearer, more extensive documentation.  But if core developers shirk 
their responsibility in this area, we will continue to suffer from a chronic 
shortage of good, current kernel documentation.

--
Daniel


      parent reply	other threads:[~2002-01-24 18:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-24  3:36 info
2002-01-24  6:54 ` David Beckett
2002-01-24 12:05 ` Rik van Riel
2002-01-24 12:59   ` Dave Jones
2002-01-24 16:06 ` Denis Vlasenko
2002-01-24 12:21   ` Rik van Riel
2002-01-24 15:06   ` Olaf Dietsche
2002-01-24 15:13     ` Rik van Riel
2002-01-24 21:54       ` Mika Liljeberg
2002-01-25 16:51         ` Mika Liljeberg
2002-01-24 16:40     ` Richard Gooch
2002-01-24 18:21   ` Daniel Phillips [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=E16ToWW-0002mj-00@starship.berlin \
    --to=phillips@bonn-fries.net \
    --cc=info@global-digicom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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

all inboxes | Powered by JetHome®