aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/HOWTO
diff options
context:
space:
mode:
authorSteven Whitehouse <swhiteho@redhat.com>2006-10-02 08:45:08 -0400
committerSteven Whitehouse <swhiteho@redhat.com>2006-10-02 08:45:08 -0400
commit59458f40e25915a355d8b1d701425fe9f4f9ea23 (patch)
treef1c9a2934df686e36d75f759ab7313b6f0e0e5f9 /Documentation/HOWTO
parent825f9075d74028d11d7f5932f04e1b5db3022b51 (diff)
parentd834c16516d1ebec4766fc58c059bf01311e6045 (diff)
Merge branch 'master' into gfs2
Diffstat (limited to 'Documentation/HOWTO')
-rw-r--r--Documentation/HOWTO20
1 files changed, 20 insertions, 0 deletions
diff --git a/Documentation/HOWTO b/Documentation/HOWTO
index 1d6560413cc5..d6f3dd1a3464 100644
--- a/Documentation/HOWTO
+++ b/Documentation/HOWTO
@@ -375,6 +375,26 @@ of information is needed by the kernel developers to help track down the
375problem. 375problem.
376 376
377 377
378Managing bug reports
379--------------------
380
381One of the best ways to put into practice your hacking skills is by fixing
382bugs reported by other people. Not only you will help to make the kernel
383more stable, you'll learn to fix real world problems and you will improve
384your skills, and other developers will be aware of your presence. Fixing
385bugs is one of the best ways to earn merit amongst the developers, because
386not many people like wasting time fixing other people's bugs.
387
388To work in the already reported bug reports, go to http://bugzilla.kernel.org.
389If you want to be advised of the future bug reports, you can subscribe to the
390bugme-new mailing list (only new bug reports are mailed here) or to the
391bugme-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
378Mailing lists 398Mailing lists
379------------- 399-------------
380 400