public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olaf Dietsche <olaf.dietsche--list.linux-kernel@exmail.de>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: linux-kernel@vger.kernel.org
Subject: Re: White Paper on the Linux kernel VM?
Date: 24 Jan 2002 16:06:37 +0100	[thread overview]
Message-ID: <873d0vss8y.fsf@tigram.bogus.local> (raw)
In-Reply-To: <20020124033618.20653.cpmta@c001.snv.cp.net> <200201241206.g0OC66E10502@Port.imtp.ilyichevsk.odessa.ua>

Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua> writes:

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

I don't want to judge, wether writing docs wastes developer's
time. But, when I first tried understanding file systems, it was of
tremendous help having docs like Documentation/filesystems/vfs.txt and
the like. I couldn't have done it without.

> After you got to understand how Linux VM works from source, feel free to 
> write docs.

When you're that far, you are a developer and it will waste your time
writing docs ;-).

Regards, Olaf.

  parent reply	other threads:[~2002-01-24 15:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-24  3:36 White Paper on the Linux kernel VM? 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 [this message]
2002-01-24 15:13     ` Rik van Riel
2002-01-24 16:40       ` Richard Gooch
2002-01-24 21:54       ` Mika Liljeberg
2002-01-25 16:51         ` Mika Liljeberg
2002-01-24 18:21   ` Daniel Phillips

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=873d0vss8y.fsf@tigram.bogus.local \
    --to=olaf.dietsche--list.linux-kernel@exmail.de \
    --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