From: Ben Bridgwater <bennyb@ntplx.net>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Background to the argument about CML2 design philosophy
Date: Sun, 20 May 2001 23:01:42 -0400 [thread overview]
Message-ID: <3B088516.68D57DB1@ntplx.net> (raw)
> derive MVME147_SCSI from MVME147 & SCSI
It seems that the preferred semantics would be:
default MVME147_SCSI from MVME147 & SCSI
That way the platform defines sane defaults, but no flexibility has been
taken away.
Presumably many of these defaulted options would also be ones that would
be configured not to be changeable in novice mode. The novice gets the
vanilla platform defaults without being bothered by detailed options,
and can switch to expert mode if they need more control. The experts get
all the options presented, but also get to benefit from the smart
platform defaults.
Ben
next reply other threads:[~2001-05-21 3:06 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 3:01 Ben Bridgwater [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-21 19:05 Background to the argument about CML2 design philosophy Wayne.Brown
2001-05-21 17:36 Wayne.Brown
2001-05-21 17:58 ` Eric S. Raymond
2001-05-21 20:00 ` Urban Widmark
2001-05-22 2:42 ` Eric S. Raymond
2001-05-22 14:42 ` john slee
2001-05-22 17:28 ` Daniel Phillips
2001-05-18 14:53 CML2 design philosophy heads-up Eric S. Raymond
2001-05-18 15:11 ` Arjan van de Ven
2001-05-18 15:26 ` Eric S. Raymond
2001-05-18 15:37 ` Arjan van de Ven
2001-05-18 15:49 ` Eric S. Raymond
2001-05-20 11:19 ` David Woodhouse
2001-05-20 15:18 ` Eric S. Raymond
2001-05-20 15:34 ` David Woodhouse
2001-05-20 15:44 ` Eric S. Raymond
2001-05-20 15:56 ` David Woodhouse
2001-05-20 17:14 ` Background to the argument about CML2 design philosophy Eric S. Raymond
2001-05-21 0:45 ` Jes Sorensen
2001-05-21 9:14 ` Helge Hafting
2001-05-21 11:32 ` Jonathan Morton
2001-05-22 20:38 ` Eric S. Raymond
2001-05-21 12:15 ` David Woodhouse
2001-05-21 12:31 ` Alan Cox
2001-05-21 23:11 ` Jonathan Morton
2001-05-20 17:47 ` David Woodhouse
2001-05-20 20:47 ` Eric S. Raymond
2001-05-20 20:59 ` Arjan van de Ven
2001-05-20 21:10 ` Robert M. Love
2001-05-21 3:38 ` Nicolas Pitre
2001-05-20 22:51 ` David Woodhouse
2001-05-21 1:13 ` Eric S. Raymond
2001-05-21 6:41 ` David Woodhouse
2001-05-21 10:04 ` Eric S. Raymond
2001-05-21 11:05 ` David Woodhouse
2001-05-21 20:38 ` John Stoffel
2001-05-22 0:59 ` Keith Owens
2001-05-22 9:24 ` Daniel Phillips
2001-05-23 1:51 ` Keith Owens
2001-05-21 23:00 ` Jonathan Morton
2001-05-22 13:45 ` David Woodhouse
2001-05-22 16:21 ` John Stoffel
2001-05-22 17:17 ` David Woodhouse
2001-05-21 3:33 ` Nicolas Pitre
2001-05-20 20:59 ` David Woodhouse
2001-05-20 18:31 ` Jonathan Morton
2001-05-20 20:13 ` Eric S. Raymond
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=3B088516.68D57DB1@ntplx.net \
--to=bennyb@ntplx.net \
--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