Revert "HOWTO: bug report addition" (or "HOWTO: mention bughunting")

This reverts commit 722385f75efd82d9f480f0765a1e97a4d83cac0d (or commit
3f27100872b21e4cc70d07b96eeb3611b30bce63, it's your choice ;), since the
same patch to Documentation/HOWTO got added twice because it just kept
applying cleanly.

Noted by Qi Yong.

Cc: Qi Yong <qiyong@fc-cn.com>
Acked-by: Diego Calleja <diegocg@gmail.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

-20
-20
Documentation/HOWTO
··· 396 397 398 399 - Managing bug reports 400 - -------------------- 401 - 402 - One of the best ways to put into practice your hacking skills is by fixing 403 - bugs reported by other people. Not only you will help to make the kernel 404 - more stable, you'll learn to fix real world problems and you will improve 405 - your skills, and other developers will be aware of your presence. Fixing 406 - bugs is one of the best ways to get merits among other developers, because 407 - not many people like wasting time fixing other people's bugs. 408 - 409 - To work in the already reported bug reports, go to http://bugzilla.kernel.org. 410 - If you want to be advised of the future bug reports, you can subscribe to the 411 - bugme-new mailing list (only new bug reports are mailed here) or to the 412 - bugme-janitor mailing list (every change in the bugzilla is mailed here) 413 - 414 - http://lists.osdl.org/mailman/listinfo/bugme-new 415 - http://lists.osdl.org/mailman/listinfo/bugme-janitors 416 - 417 - 418 - 419 Mailing lists 420 ------------- 421
··· 396 397 398 399 Mailing lists 400 ------------- 401