From: "Dennis Grant" <trog@wincom.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
dpaun@rogers.com, Rusty Lynch <rusty@linux.co.intel.com>,
trog@wincom.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: A Kernel Configuration Tale of Woe
Date: Tue, 26 Nov 2002 14:28:29 -0500 [thread overview]
Message-ID: <3de3cc8d.54dd.0@wincom.net> (raw)
>On Tue, 2002-11-26 at 18:04, Dimitrie O. Paun wrote:
>> On November 26, 2002 12:35 pm, Rusty Lynch wrote:
>>> So how would you deal with somebody contributing bogus
>>> mappings? What if somebody was just wrong, or uploading a
>>> mapping in error?
>> The same applies to the kernel code, or any other open
>> source project: How do you deal with somebody contributing
>> bogus code?
>> Somehow things work out, as we have already witnessed.
> For boards its not that simple. Many vendors release multiple > utterly different
machines with the same box, bios and ident.
> The customer is told "IDE CD, 100mbit ethernet", the customer
> gets random cheapest going ethernet.
Agreed - so then the association between "board" and "chipset" must be capable
of being multi-valued, and when there is a mult-valued match there must be some
means of further interrogating the user (or user agent) for more information.
DG
next reply other threads:[~2002-11-26 19:12 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 19:28 Dennis Grant [this message]
2002-11-26 19:45 ` John Bradford
2002-11-27 10:55 ` Keith Owens
2002-11-27 12:03 ` Roman Zippel
2002-11-27 12:19 ` Keith Owens
2002-11-27 19:01 ` Sam Ravnborg
2002-11-27 19:14 ` Kai Germaschewski
2002-11-26 20:05 ` Alan Cox
2002-11-26 23:21 ` Roger Gammans
2002-11-27 6:10 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2002-11-27 17:52 Dennis Grant
2002-11-27 18:01 ` Alex Riesen
2002-11-27 17:47 Mark H. Wood
[not found] <fa.gaum5rv.1j3snhh@ifi.uio.no>
[not found] ` <fa.ivlir9v.u14v3p@ifi.uio.no>
2002-11-27 8:43 ` Giacomo Catenazzi
2002-11-27 10:12 ` John Bradford
2002-11-26 17:57 Dennis Grant
2002-11-26 18:11 ` Andrew Walrond
2002-11-26 18:24 ` Rusty Lynch
2002-11-26 23:46 ` Lee Leahu
2002-11-26 15:35 Dennis Grant
2002-11-26 17:01 ` Kai Henningsen
2002-11-26 17:35 ` Rusty Lynch
2002-11-26 18:04 ` Dimitrie O. Paun
2002-11-26 18:46 ` Alan Cox
2002-11-26 18:48 ` Richard B. Johnson
2002-11-26 9:15 Thomas Hood
2002-11-25 19:30 Dennis Grant
2002-11-25 20:00 ` Richard B. Johnson
2002-11-26 10:57 ` Adrian Bunk
2002-11-26 14:44 ` Alan Cox
2002-11-26 12:33 ` Andrew Walrond
2002-11-28 22:09 ` LA Walsh
2002-11-29 1:28 ` Miles Bader
2002-11-29 10:04 ` Andrew Walrond
2002-11-29 10:21 ` Miles Bader
2002-11-25 17:33 Dennis Grant
2002-11-25 18:10 ` Richard B. Johnson
2002-11-25 18:58 ` Samuel Flory
2002-11-26 16:58 ` Kai Henningsen
2002-11-26 4:24 ` Theodore Ts'o
2002-11-26 8:21 ` john slee
2002-11-26 8:35 ` Brad Hards
2002-11-26 19:59 ` Otto Wyss
2002-11-27 0:29 ` Alan Cox
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=3de3cc8d.54dd.0@wincom.net \
--to=trog@wincom.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dpaun@rogers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@linux.co.intel.com \
/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®