All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pranith Kumar D <pranith-kumar_d@mentor.com>
To: greg@kroah.com, penberg@cs.helsinki.fi,
	linux-kernel@vger.kernel.org, debiandev@gmail.com
Subject: [PATCH 1/1] FIX HOWTO: removing duplicated entry.
Date: Fri, 18 May 2007 19:42:44 +0530	[thread overview]
Message-ID: <464DB45C.8070200@mentorg.com> (raw)

Hello,
    Sorry for submitting the previous patch without description, name 
signed off line.

This removes the duplicated paragraph in the Documentation/HOWTO file.

Signed-off-by: D Pranith Kumar<pranith-kumar_d@mentorg.com>

--- linux-2.6.21.1/Documentation/HOWTO.orig	2007-05-18 18:54:18.000000000 +0530
+++ linux-2.6.21.1/Documentation/HOWTO	2007-05-18 18:55:03.000000000 +0530
@@ -383,26 +383,6 @@ One of the best ways to put into practic
 bugs reported by other people. Not only you will help to make the kernel
 more stable, you'll learn to fix real world problems and you will improve
 your skills, and other developers will be aware of your presence. Fixing
-bugs is one of the best ways to earn merit amongst the developers, because
-not many people like wasting time fixing other people's bugs.
-
-To work in the already reported bug reports, go to http://bugzilla.kernel.org.
-If you want to be advised of the future bug reports, you can subscribe to the
-bugme-new mailing list (only new bug reports are mailed here) or to the
-bugme-janitor mailing list (every change in the bugzilla is mailed here)
-
-	http://lists.osdl.org/mailman/listinfo/bugme-new
-	http://lists.osdl.org/mailman/listinfo/bugme-janitors
-
-
-
-Managing bug reports
---------------------
-
-One of the best ways to put into practice your hacking skills is by fixing
-bugs reported by other people. Not only you will help to make the kernel
-more stable, you'll learn to fix real world problems and you will improve
-your skills, and other developers will be aware of your presence. Fixing
 bugs is one of the best ways to get merits among other developers, because
 not many people like wasting time fixing other people's bugs.
 




                 reply	other threads:[~2007-05-18 14:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=464DB45C.8070200@mentorg.com \
    --to=pranith-kumar_d@mentor.com \
    --cc=debiandev@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.