From: Rene Herman <rene.herman@keyaccess.nl>
To: Ray Lee <ray-lk@madrabbit.org>
Cc: Roel Kluin <12o3l@tiscali.nl>, Rik van Riel <riel@redhat.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] return hidden bug
Date: Tue, 23 Oct 2007 02:15:01 +0200 [thread overview]
Message-ID: <471D3D05.9070801@keyaccess.nl> (raw)
In-Reply-To: <2c0942db0710221600j24f76f68lefe562cc8bc2d067@mail.gmail.com>
On 10/23/2007 01:00 AM, Ray Lee wrote:
> On 10/22/07, Rene Herman <rene.herman@keyaccess.nl> wrote:
>> Hugely trust inspiring isn't it -- the amount of eyes and comments you'll
>> get even on trivial patches like this? This development model is working!
>
> Go easy with the snarkiness, hmm? It's the trivial ones that seem to
> be the most dangerous. The larger ones actually get *tested*
> sometimes.
I was also commenting and don't generally on anything much more involved so
any snarkiness included myself which should make things better.
>> Now if only we'd sometimes get some for non trivial patches as well...
>
> That's certainly true regardless, but for myself, I'd rather throw
> some reviews out for the small ones since I have adequate time and
> knowledge for them. The larger ones require domain specific knowledge
> I lack, and time I don't have.
Exactly the problem. Comment was mostly triggered due to me looking at a
problem with a proprietary CD-ROM driver again tonight that I posted a few
months ago where the only comment has been from the fellow author. There the
problem was the block layer blowing up and given that it seems unlikely that
this wouldn't be a problem inside the newbie-driver itself, that the block
part of it was actually really small and people said they'd look at it, the
subsequent thundering silence still annoys me.
Ofcourse, now it seems the kernel itself has moved on enough that the driver
doesn't work at _all_ anymore and I at the moment lack the time to spend the
required hours googling around trying to find out what the heck changed out
from under me so that I might get it to at least do what it already did do.
Hey, I don't actually know and maybe I'm just wrong but I have the feeling
that over the last 1 or 2 years most new developers seem to be either people
that are payed to be so, perhaps in the form of graduation, or janitors. The
kernel is much, much more complex than even only a few years ago and at the
same time the number of knowledgeable developers who'll do something other
than their own thing and otherwise just wait around for something perfect to
merge seems to be approaching zero.
That is -- I do not feel that the current developer base is expending overly
many efforts to appear welcoming.
Please feel free to do the open-source thing and argue that's actually an
advantage (there we have that snarkiness again...) or otherwise ignore me.
I'll just sit here and be grumpy anyway. Might be better after a good
night's sleep...
Rene.
next prev parent reply other threads:[~2007-10-23 0:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 1:05 [PATCH] return hidden bug Roel Kluin
2007-10-22 1:42 ` Rik van Riel
2007-10-22 1:53 ` Roel Kluin
2007-10-22 3:08 ` Rik van Riel
2007-10-22 5:02 ` Herbert Xu
2007-10-22 9:30 ` Pekka Enberg
2007-10-22 15:19 ` Rik van Riel
2007-10-22 15:23 ` Pekka Enberg
2007-10-22 16:42 ` Ray Lee
2007-10-22 17:56 ` Roel Kluin
2007-10-22 18:12 ` Ray Lee
2007-10-22 18:52 ` Roel Kluin
2007-10-22 22:26 ` Rene Herman
2007-10-22 23:00 ` Ray Lee
2007-10-23 0:15 ` Rene Herman [this message]
2007-10-22 18:36 ` Matt Mackall
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=471D3D05.9070801@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=12o3l@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-lk@madrabbit.org \
--cc=riel@redhat.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