[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080522082941.5431654b@infradead.org>
Date: Thu, 22 May 2008 08:29:41 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Adrian Bunk <bunk@...nel.org>
Cc: Jesper Juhl <jesper.juhl@...il.com>,
Jonathan Corbet <corbet@....net>,
Cyrill Gorcunov <gorcunov@...il.com>, rdunlap@...otime.net,
tytso@....edu, hch@...radead.org, viro@...iv.linux.org.uk,
linux-kernel@...r.kernel.org, davem@...emloft.net,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: CFD: linux-wanking@...r.kernel.org (was [PATCH] Standard
indentation of arguments)
On Thu, 22 May 2008 03:12:33 +0300
Adrian Bunk <bunk@...nel.org> wrote:
> On Thu, May 22, 2008 at 01:46:28AM +0200, Jesper Juhl wrote:
> >...
> > 2. How to find things to work on as a beginner
> >...
> > Finding bugs to fix is easy. Here are some ways to find useful work
> > to do:
> >...
>
> But fixing them is not so easy...
math is hard, lets go shopping -- Barbie
>
> Sorry for being destructive, but we do not have easy coding tasks
> for newbies.
Sorry but if it's too easy, you don't learn from it. If it's not a
challenge .... you're going to get stuck and never really learn.
>
> If it's easy it's already fixed, and dozens of people following your
> advice to look at e.g. compile or sparse warnings will only generate
> much noise, but they'll have a hard time finding anything they are
> capable to fix.
If they only go where they are already capable.. no gain for anyone.
A bug can be a challenge, and need a lot of learning and investigating.
And that's *FINE*. That's what you learn from. Not from the actual fix
itself.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists