From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S1754614AbYEVPak@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754614AbYEVPak (ORCPT <rfc822;w@1wt.eu>);
	Thu, 22 May 2008 11:30:40 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752732AbYEVPac
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Thu, 22 May 2008 11:30:32 -0400
Received: from pentafluge.infradead.org ([213.146.154.40]:54075 "EHLO
	pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752718AbYEVPab (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 22 May 2008 11:30:31 -0400
Date: Thu, 22 May 2008 08:29:41 -0700
From: Arjan van de Ven <arjan@infradead.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Jesper Juhl <jesper.juhl@gmail.com>, Jonathan Corbet <corbet@lwn.net>,
       Cyrill Gorcunov <gorcunov@gmail.com>, rdunlap@xenotime.net,
       tytso@mit.edu, hch@infradead.org, viro@zeniv.linux.org.uk,
       linux-kernel@vger.kernel.org, davem@davemloft.net,
       Andrew Morton <akpm@linux-foundation.org>
Subject: Re: CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard
 indentation of arguments)
Message-ID: <20080522082941.5431654b@infradead.org>
In-Reply-To: <20080522001233.GE16376@cs181133002.pp.htv.fi>
References: <9a8748490805211306l50b8411ax4462be18c94ca065@mail.gmail.com>
	<32279.1211401651@vena.lwn.net>
	<9a8748490805211337q1e7ceab7i80e4820c46f8171b@mail.gmail.com>
	<9a8748490805211646s5ef93f8ey43ebbc7746fb1a3b@mail.gmail.com>
	<20080522001233.GE16376@cs181133002.pp.htv.fi>
Organization: Intel
X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i386-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-SRS-Rewrite: SMTP reverse-path rewritten from <arjan@infradead.org> by pentafluge.infradead.org
	See http://www.infradead.org/rpr.html
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, 22 May 2008 03:12:33 +0300
Adrian Bunk <bunk@kernel.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.