public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-kernel@vger.kernel.org
Subject: Re: stable? quality assurance?
Date: Sun, 11 Jul 2010 16:51:42 +0200	[thread overview]
Message-ID: <201007111651.42963.Martin@lichtvoll.de> (raw)
In-Reply-To: <AANLkTimCwi2uJqqPaq3U30f3rvdDizu1BnaaXgvNeC9k@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 3155 bytes --]


Hi Lee,

Am Sonntag 11 Juli 2010 schrieb Lee Mathers:
> Wow!
> 
> First question what is a "desaster"?

For me freezing the machine or at least complete desktop randomly for 
example. And actually I said "for me" as you can reread on the bottom of 
your top posting.

> Second question, what makes you so important that you feel you can
> makes demands and comments as you did.

Since when I do need to be considered to be important by you or anyone 
else to make comments? Actually I think I do not - this is still an open 
mailinglist, isn't it? And I won't waste my time with proofs that I 
contributed to free software here and there - also to kernel testing what 
for example Ingo Molnar could testify back in early CFS times where I 
roughly compiled a kernel a day and to kernel documentation once.

I also do not get why you are attacking me personally. It seems to be that 
you feel personally attacked by me. But I did not. I just questioned the 
quality of the kernel and its current quality assurance process. No one is 
personally bad then anything of that lacks.

One reason for a demand for me is best expressed by this question: Does 
the kernel developer community want to encourage that a group of advanced 
Linux users - but mostly non-developers - compile their own vanilla or 
valnilla near kernels, provide wider testing and report a bug now and 
then?

I can live with either answer. If not, I just will be much more reluctant 
to try out new kernels.

But I have experienced working productively with kernel developers like 
Ingo and tuxonice developer Nigel who where pretty interested in my usage 
of latest kernels.

I admit my wording could have been friendlier, too, but I was just 
frustrated out of my recent experiences. What I wanted to achieve is 
raising concern whether kernel quality actually has decreased and more 
importantly something needs to be done to make it more stable again.

Well Linus has at least been a bit more reluctant to take big changes 
after rc1 this cycle, so maybe 2.6.35 will be better again.

> If indeed these are production systems and you are an administrator of
> said production systems. I suggest you need to do a little more home
> work to expand your knowledge base.

Its production system that have some fault tolerance, i.e. not servers, 
but laptops and one, not yet all workstations. But for me a certain 
balance has to be met. I will just downgrade and drop newer kernels or 
even start skipping whole major versions completely on a regular basis if 
that turns out to be the only way to have stable enough machines for me. 
One approach would be to stick to the stable kernels that Greg and the 
stable team maintains for a longer time

> Hope you have better luck in getting your systems running well.

Thanks. I certainly will. If need be by downgrading.

I hope that someone answers who actually can take some critique. From the 
current replies I perceive a lack of that ability.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-07-11 14:51 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-11  7:18 stable? quality assurance? Martin Steigerwald
2010-07-11  8:39 ` Eric Dumazet
2010-07-11 14:22   ` Martin Steigerwald
2010-07-11 14:52     ` Martin Steigerwald
2010-07-11 15:58   ` William Pitcock
2010-07-11 16:34     ` Eric Dumazet
2010-07-16  6:59     ` Greg KH
2010-08-05  3:27       ` Jeremy Fitzhardinge
2010-07-11 17:04   ` Heinz Diehl
2010-07-11 13:16 ` Ted Ts'o
2010-07-11 18:02   ` Anca Emanuel
2010-07-12  6:46   ` David Newall
     [not found]     ` <AANLkTilGjfx9sb66qVfZn1SeFPURHUrrdE7JCrild8VX@mail.gmail.com>
2010-07-12 12:35       ` Fwd: " Marcin Letyns
2010-07-12 12:42         ` Alexey Dobriyan
     [not found]           ` <AANLkTik64lxDiCN-eRo3i_-cTqAvCzbaRI4EEXoD44Vj@mail.gmail.com>
2010-07-12 12:52             ` Fwd: " Marcin Letyns
2010-07-12 14:57           ` Valdis.Kletnieks
2010-07-12 15:56       ` David Newall
2010-07-12 17:48         ` Marcin Letyns
2010-07-12 18:00         ` Stefan Richter
2010-07-12 19:58           ` David Newall
2010-07-12 21:11             ` Stefan Richter
2010-07-12 21:39             ` Martin Steigerwald
2010-07-12 22:44               ` Stefan Richter
2010-07-15  7:23             ` david
2010-07-13 16:50         ` Theodore Tso
2010-07-13 20:45           ` David Newall
2010-07-14  6:33             ` Theodore Tso
2010-09-04 17:12   ` Martin Steigerwald
2010-07-11 13:56 ` Lee Mathers
2010-07-11 14:51   ` Martin Steigerwald [this message]
2010-07-11 17:22     ` Willy Tarreau
2010-07-11 21:38       ` Rafael J. Wysocki
2010-07-12  4:17         ` Willy Tarreau
2010-07-12  9:56       ` Martin Steigerwald
2010-07-12 15:43       ` Martin Steigerwald
2010-07-12 17:36         ` Willy Tarreau
2010-07-12 19:56           ` Martin Steigerwald
2010-07-12 23:03             ` Stefan Richter
2010-07-13 10:30               ` Martin Steigerwald
2010-07-15  7:32               ` david
2010-07-12 17:55         ` Stefan Richter
2010-09-04 16:38       ` Martin Steigerwald
2010-09-04 18:46         ` Ted Ts'o
2010-09-04 19:11           ` Martin Steigerwald
2010-09-04 23:23             ` Ted Ts'o
2010-09-05  7:59               ` Martin Steigerwald
2010-09-04 19:24         ` Stefan Richter
2010-09-04 19:34           ` Stefan Richter
2010-09-04 20:21           ` Martin Steigerwald
2010-09-04 22:50             ` Stefan Richter
2010-09-04 23:16             ` Ted Ts'o
2010-09-05  8:35         ` Avi Kivity
2010-09-05  9:48           ` Martin Steigerwald
2010-07-11 19:49     ` Stefan Richter
2010-07-13 11:11     ` Alejandro Riveira Fernández
2010-07-13 12:50       ` rt2x00: slow wifi with correct basic rate bitmap (was Re: stable? quality assurance?) Stefan Richter
2010-07-13 15:35         ` John W. Linville
2010-07-13 18:19           ` Alejandro Riveira Fernández
2010-07-13 18:38             ` John W. Linville
2010-07-13 19:07               ` Alejandro Riveira Fernández
2010-07-13 18:06         ` Alejandro Riveira Fernández
2010-07-13 19:18           ` Stefan Richter
2010-07-12 19:46 ` stable? quality assurance? Nix
     [not found] ` <AANLkTimEdVsmIgXBbmhsq75ElQvGAI8avsM8-wlDpm4z@mail.gmail.com>
2010-07-15  9:09   ` Valeo de Vries
2010-07-16  7:00     ` Greg KH
2010-07-16  7:19       ` Justin P. Mattock
2010-07-16 15:25       ` Randy Dunlap
2010-07-16 15:34       ` Valeo de Vries
  -- strict thread matches above, loose matches on Subject: below --
2010-09-04 16:42 Martin Steigerwald
2010-09-04 17:22 ` Willy Tarreau
2010-09-04 19:33   ` Martin Steigerwald
2010-09-04 20:19     ` Willy Tarreau

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=201007111651.42963.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --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