Fwd: [BUG] HOWTO

Fwd: [BUG] HOWTO

[debian developer]

---------- Forwarded message ----------
From: debian developer <debiandev@gmail.com>
Date: May 18, 2007 4:24 PM
Subject: [BUG] HOWTO
To: greg@kroah.com, linux-kernel@vger.kernel.org


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

Fwd: [BUG] HOWTO

[debian developer]

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

Re: [BUG] HOWTO

[Greg KH]

On Fri, May 18, 2007 at 04:24:59PM +0530, debian developer wrote:
>  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.

Can you take a look at Documentation/SubmittingPatches and generate a
patch in the format that is described there?  That way I can apply this
to fix the problem.

thanks,

greg k-h

[PATCH] Fix duplicated entry in Documentation/HOWTO

[Junio C Hamano]

Commit 3f271008 introduced this section to Linus tree, but a
later commit 722385f7 accepted almost the identical patch via
Greg's tree, both from the same author.

This kills the duplicated one.

Signed-off-by: Junio C Hamano <junkio@cox.net>
---
 Documentation/HOWTO |   20 --------------------
 1 files changed, 0 insertions(+), 20 deletions(-)

diff --git a/Documentation/HOWTO b/Documentation/HOWTO
index 48123db..ced9207 100644
--- a/Documentation/HOWTO
+++ b/Documentation/HOWTO
@@ -396,26 +396,6 @@ bugme-janitor mailing list (every change in the bugzilla is mailed here)
 
 
 
-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.
-
-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
-
-
-
 Mailing lists
 -------------