From: Mark Nipper <nipsy@bitgnome.net>
To: "Martin MOKREJŠ" <mmokrejs@ribosome.natur.cuni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Giving developers clue how many testers verified certain kernel version
Date: Thu, 21 Jul 2005 21:10:46 -0500 [thread overview]
Message-ID: <20050722021046.GB21727@king.bitgnome.net> (raw)
In-Reply-To: <42E04D11.20005@ribosome.natur.cuni.cz>
I have a different idea along these lines but not using
bugzilla. A nice system for tracking usage of certain components
might be made by having people register using a certain e-mail
address and then submitting their .config as they try out new
versions of kernels.
The idea of course is that people will generally only
have compiled their own custom kernels with the drivers and
components they tend to use most. It might be enough to ask
people who use this system to only submit mostly customized
configurations as opposed to distribution style kernel
configurations where almost everything is compiled as a module.
Anyway, the end result being that kernel developers could
ultimately refer to this system and see as they change things
whether a lot of people are hitting the components in the kernel
which might have been affected by their changes. If even one
hundred people report using some specific subsystem which has
recently undergone significant change without any reports of
problems, then the developer can rest somewhat more easily
knowing their changes were probably made without incident.
Just an idea. It might require some minimum
recommendations to users willing to participate. I know for
example that I statically compile all four I/O schedulers in all
my kernels currently even though I always let the kernel select
whichever is the default and never change it myself. Obviously
it would make more sense for me to axe those schedulers which are
not absolutely necessary to make whatever statistics being
gathered on my particular configuration more useful to a
developer checking to see which schedulers are being used and to
what extent.
--
Mark Nipper e-contacts:
4475 Carter Creek Parkway nipsy@bitgnome.net
Apartment 724 http://nipsy.bitgnome.net/
Bryan, Texas, 77802-4481 AIM/Yahoo: texasnipsy ICQ: 66971617
(979)575-3193 MSN: nipsy@tamu.edu
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GG/IT d- s++:+ a- C++$ UBL++++$ P--->+++ L+++$ !E---
W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--)
Y+ PGP t+ 5 X R tv b+++@ DI+(++) D+ G e h r++ y+(**)
------END GEEK CODE BLOCK------
---begin random quote of the moment---
This sentence no verb.
----end random quote of the moment----
next prev parent reply other threads:[~2005-07-22 2:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 1:34 Martin MOKREJŠ
2005-07-22 2:10 ` Mark Nipper [this message]
2005-07-22 2:38 ` Martin MOKREJŠ
2005-07-22 2:40 ` Alejandro Bonilla
2005-07-22 23:22 ` Adrian Bunk
2005-07-22 23:11 ` Adrian Bunk
2005-07-24 18:45 ` Martin MOKREJŠ
2005-07-24 18:54 ` Adrian Bunk
2005-07-24 19:10 ` Martin MOKREJŠ
2005-07-23 0:44 Blaisorblade
2005-07-23 0:50 ` David Lang
2005-07-23 0:59 ` H. Peter Anvin
2005-07-23 1:07 ` Alejandro Bonilla
2005-07-23 3:09 ` Lee Revell
2005-07-23 2:15 ` Alejandro Bonilla
2005-07-23 3:21 ` Lee Revell
2005-07-23 2:34 ` Alejandro Bonilla
2005-07-23 3:31 ` Linus Torvalds
2005-07-23 2:40 ` Alejandro Bonilla
2005-07-23 3:34 ` Lee Revell
2005-07-23 9:05 ` Con Kolivas
2005-07-23 16:45 ` Lee Revell
2005-07-23 3:56 ` Adrian Bunk
2005-07-23 9:21 ` Jesper Krogh
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=20050722021046.GB21727@king.bitgnome.net \
--to=nipsy@bitgnome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mmokrejs@ribosome.natur.cuni.cz \
/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®