From: Mike Fedyk <mfedyk@matchmail.com>
To: Grigor Gatchev <grigor@zadnik.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A Layered Kernel: Proposal
Date: Fri, 27 Feb 2004 10:27:03 -0800 [thread overview]
Message-ID: <403F8BF7.3040202@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0402271151040.26240-100000@lugburz.zadnik.org>
Grigor Gatchev wrote:
>
> On Thu, 26 Feb 2004, Mike Fedyk wrote:
>>Useful discussion would be asking for implementation suggestions to get
>>to your goal. Oh wait, I think there are already some of those in this
>>thread.
>
>
> Wait, wait a bit :-) I am still trying to see if that attractively looking
> model is really good. After (rather, _if_) it is proven good, I would be
> asking for implementation suggestions. But let's see first if it is worth
> implementing.
OK, you need to state that in simple terms at the very begining of your
proposal in the future. Otherwise many people won't understand you're
asking for design help, and are just asking others to do what you want.
Also, fill in more details. Take all of the ideas against your proposal
in this thread, and write how they can be overcome. You have to give
enough detail so it will not be seen as a dismissal of said problem, and
enough flexability for a design document.
Frankly, it might be better if you wrote an RFC with implementation details.
HTH,
Mike
next prev parent reply other threads:[~2004-02-27 18:27 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 20:05 A Layered Kernel: Proposal Grigor Gatchev
2004-02-24 22:31 ` Rik van Riel
2004-02-25 9:08 ` Grigor Gatchev
2004-02-25 12:52 ` Rik van Riel
2004-02-25 13:23 ` Richard B. Johnson
2004-02-25 15:08 ` Grigor Gatchev
2004-02-25 15:42 ` Richard B. Johnson
2004-02-25 16:01 ` Nikita Danilov
2004-02-25 19:25 ` Christer Weinigel
2004-02-25 19:46 ` Grigor Gatchev
2004-02-25 23:40 ` Timothy Miller
2004-02-26 0:55 ` Rik van Riel
2004-02-26 15:43 ` Jesse Pollard
2004-02-26 17:12 ` Rik van Riel
2004-02-27 9:45 ` Grigor Gatchev
2004-02-26 11:03 ` Grigor Gatchev
2004-02-26 5:59 ` jw schultz
2004-02-29 12:32 ` Christer Weinigel
2004-02-29 14:48 ` Grigor Gatchev
2004-03-01 6:07 ` Mike Fedyk
2004-03-06 18:51 ` Grigor Gatchev
2004-03-08 3:11 ` Mike Fedyk
2004-03-08 12:23 ` Grigor Gatchev
2004-03-08 17:39 ` Theodore Ts'o
2004-03-08 20:41 ` viro
2004-03-09 19:12 ` Grigor Gatchev
2004-03-09 21:03 ` Timothy Miller
2004-03-09 23:24 ` Mike Fedyk
2004-03-08 18:41 ` Mike Fedyk
2004-03-08 21:33 ` Paul Jackson
2004-02-25 14:44 ` Grigor Gatchev
2004-02-24 22:54 ` Mike Fedyk
2004-02-25 10:03 ` Grigor Gatchev
2004-02-25 19:58 ` Mike Fedyk
2004-02-25 21:59 ` Grigor Gatchev
2004-02-25 22:22 ` Mike Fedyk
2004-02-26 11:46 ` Grigor Gatchev
2004-02-26 12:17 ` Jens Axboe
2004-02-26 16:37 ` Grigor Gatchev
2004-02-26 18:12 ` Christoph Hellwig
2004-02-26 19:23 ` Mike Fedyk
2004-02-27 11:18 ` Grigor Gatchev
2004-02-27 18:05 ` Tim Hockin
2004-02-27 18:34 ` Richard B. Johnson
2004-02-27 18:27 ` Mike Fedyk [this message]
2004-02-28 0:26 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2004-02-24 20:28 Carlos Silva
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=403F8BF7.3040202@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=grigor@zadnik.org \
--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