From: klink@clouddancer.com (Colonel)
To: linux-kernel@vger.kernel.org
Subject: Re: What are the VM motivations??
Date: Mon, 25 Jun 2001 08:46:49 -0700 (PDT) [thread overview]
Message-ID: <20010625154649.820E4784D9@mail.clouddancer.com> (raw)
In-Reply-To: <9h6d6b$509$1@ns1.clouddancer.com>
In-Reply-To: <20010621190103.A888@jmcmullan.resilience.com> <9h6916$4og$1@ns1.clouddancer.com> <20010625034427.65260784D9@mail.clouddancer.com> <01062506044500.16624@starship> <20010625034427.65260784D9@mail.clouddancer.com> <9h6d6b$509$1@ns1.clouddancer.com>
>> POST IT. Give the rest of us some clues and the opportunity to check
>> evaluator's replies.
>
>Well, if you try that strategy you'll find you never get around to posting it
>because you'll be too worried about getting it right. The point is not to
>get it right, it's to get a starting point down on (virtual) paper. I'd
>strongly suggest passing something like that around for comment privately
>first.
Well, it does seem that some ego is involved here...
>
>*Then* post it.
>
>(and convince me you're not just talking)
As a physicist, I learned long ago that if you cannot use the back of
an envelope and explain your theory to a secretary, you do not
understand it. It has only been revealed recently where some VM
design information may be hidden, and it's apparently out of date.
Maintenance requires good documentation, especially in critical areas.
I hope that your suggestion succeeds, and that a document is passed
around, but I'll bet a large amount that it doesn't happen.
If everyone is in the dark, it gets difficult to criticize the guy
with a match and leaves the matchholder in charge. Some matchholders
want it that way.
next prev parent reply other threads:[~2001-06-25 15:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 23:01 What are the VM motivations?? Jason McMullan
2001-06-21 23:32 ` [OT] " Justin Guyett
2001-06-22 1:13 ` Rik van Riel
2001-06-22 0:23 ` Rik van Riel
2001-06-23 20:23 ` watermodem
2001-07-01 23:58 ` Mark H. Wood
2001-06-23 2:03 ` Marcelo Tosatti
2001-06-24 15:04 ` Rik van Riel
2001-06-24 18:01 ` Jason McMullan
2001-06-24 18:26 ` Rik van Riel
2001-06-24 18:52 ` Jason McMullan
2001-06-24 19:29 ` Rik van Riel
2001-06-24 20:29 ` Jason McMullan
2001-06-24 20:49 ` Rik van Riel
2001-06-24 20:39 ` Jonathan Morton
2001-06-24 20:33 ` Stephen Satchell
2001-06-25 1:46 ` Russell Leighton
2001-06-25 2:53 ` Daniel Phillips
[not found] ` <9h6916$4og$1@ns1.clouddancer.com>
2001-06-25 3:44 ` Colonel
2001-06-25 4:04 ` Daniel Phillips
[not found] ` <9h6d6b$509$1@ns1.clouddancer.com>
2001-06-25 15:46 ` Colonel [this message]
2001-06-25 16:25 ` Daniel Phillips
2001-06-25 17:53 ` Rik van Riel
2001-06-25 17:48 ` Rik van Riel
[not found] ` <9h4vln$2tg$1@ns1.clouddancer.com>
2001-06-24 16:15 ` Colonel
2001-06-24 16:34 ` Rik van Riel
2001-06-24 19:11 ` Henning P. Schmiedehausen
[not found] ` <9h54u8$341$1@ns1.clouddancer.com>
2001-06-25 3:40 ` Colonel
2001-07-01 14:43 ` Mark H. Wood
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=20010625154649.820E4784D9@mail.clouddancer.com \
--to=klink@clouddancer.com \
--cc=linux-kernel@vger.kernel.org \
/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