[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4739FA4D.1050900@rtr.ca>
Date: Tue, 13 Nov 2007 14:26:05 -0500
From: Mark Lord <liml@....ca>
To: Adrian Bunk <bunk@...nel.org>
Cc: Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
David Miller <davem@...emloft.net>, protasnb@...il.com,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
alsa-devel@...a-project.org, linux-ide@...r.kernel.org,
linux-pcmcia@...ts.infradead.org,
linux-input@...ey.karlin.mff.cuni.cz,
bugme-daemon@...zilla.kernel.org
Subject: Re: [BUG] New Kernel Bugs
Adrian Bunk wrote:
> On Tue, Nov 13, 2007 at 01:47:10PM -0500, Mark Lord wrote:
>> Adrian Bunk wrote:
..
> Another point is that it shifts the work from the few experienced
> developers to the many users. Users (and voluntary testers) we have
> many, but developer time for debugging bug reports is a quite scarce
> resource.
>
>> And when a "maintainer" is too busy to find/fix their own bugs,
>> that could be a sign that they've bitten off too big of a chunk
>> of the kernel, and it's time for them to distribute code maintainership.
>
> The problem is: Maintainers don't grow on trees.
..
Hey, if somebody has time to break things, then they damn well ought
to be able to make time to fix them again. And the best developers
here on LKML do just that (fix what they break).
You broke it, you fix it. A simple rule.
Translation for the particularly daft:
If you've been making significant updates to a driver/subsystem,
and people are reporting that it is now broken for them,
then it's your job to make it right. The reporters can help,
and many may even git-bisect or send patches.
But you cannot *expect* or *insist* upon them doing your job.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists