Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758085AbXERMlQ (ORCPT ); Fri, 18 May 2007 08:41:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754338AbXERMlG (ORCPT ); Fri, 18 May 2007 08:41:06 -0400 Received: from wr-out-0506.google.com ([64.233.184.234]:61188 "EHLO wr-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754522AbXERMlF (ORCPT ); Fri, 18 May 2007 08:41:05 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oQg6Wg5Gy/dK+1FTOPCOw7iqS4p58c4TvEn5JAO9T13o77E+u7hgkjPLhDy9hhScbTO78AxiMZtNHKrhA5rMCqTDjA3nb1eBeBe6vfKkniosZFW+3vSJoBqjoAlbwzMbH6aP2Tk3yBscub6/8jp/PcpBsVgrcREaoY+1yajBlxg= Message-ID: Date: Fri, 18 May 2007 18:10:57 +0530 From: "debian developer" To: linux-kernel@vger.kernel.org, debiandev@gmail.com Subject: Fwd: [BUG] HOWTO In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2350 Lines: 76 There is a repetition of the below para in the HOWTO. :) sorry, me being newbie( thts y i was goin thru the HOWTO) cannot write the PATCH for this. Please correct it. 378 Managing bug reports 379 -------------------- 380 381 One of the best ways to put into practice your hacking skills is by fixing 382 bugs reported by other people. Not only you will help to make the kernel 383 more stable, you'll learn to fix real world problems and you will improve 384 your skills, and other developers will be aware of your presence. Fixing 385 bugs is one of the best ways to earn merit amongst the developers, because 386 not many people like wasting time fixing other people's bugs. 387 388 To work in the already reported bug reports, go to http://bugzilla.kernel.org. 389 If you want to be advised of the future bug reports, you can subscribe to the 390 bugme-new mailing list (only new bug reports are mailed here) or to the 391 bugme-janitor mailing list (every change in the bugzilla is mailed here) 392 393 http://lists.osdl.org/mailman/listinfo/bugme-new 394 http://lists.osdl.org/mailman/listinfo/bugme-janitors 395 396 397 398 Managing bug reports 399 -------------------- 400 401 One of the best ways to put into practice your hacking skills is by fixing 402 bugs reported by other people. Not only you will help to make the kernel 403 more stable, you'll learn to fix real world problems and you will improve 404 your skills, and other developers will be aware of your presence. Fixing 405 bugs is one of the best ways to get merits among other developers, because 406 not many people like wasting time fixing other people's bugs. 407 408 To work in the already reported bug reports, go to http://bugzilla.kernel.org. 409 If you want to be advised of the future bug reports, you can subscribe to the 410 bugme-new mailing list (only new bug reports are mailed here) or to the 411 bugme-janitor mailing list (every change in the bugzilla is mailed here) 412 413 http://lists.osdl.org/mailman/listinfo/bugme-new 414 http://lists.osdl.org/mailman/listinfo/bugme-janitors 415 416 417 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/