Commit:     1a93fa86bf6eb0d8bed84ef18c8b35be389edee5
Parent:     900f1d2c87738919986c6de606336057674c8c1e
Author:     Linus Torvalds <[EMAIL PROTECTED]>
AuthorDate: Thu May 24 08:50:39 2007 -0700
Committer:  Linus Torvalds <[EMAIL PROTECTED]>
CommitDate: Thu May 24 08:50:39 2007 -0700

    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 <[EMAIL PROTECTED]>
    Acked-by: Diego Calleja <[EMAIL PROTECTED]>
    Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
 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
-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)
 Mailing lists
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to