From: "debian developer" <debiandev@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Fwd: [BUG] HOWTO
Date: Fri, 18 May 2007 16:26:28 +0530 [thread overview]
Message-ID: <f24d23310705180356p3fd4715p310641d27fb36cbf@mail.gmail.com> (raw)
In-Reply-To: <f24d23310705180354l2995a89fhb513fe3e54221784@mail.gmail.com>
---------- 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
next parent reply other threads:[~2007-05-18 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f24d23310705180354l2995a89fhb513fe3e54221784@mail.gmail.com>
2007-05-18 10:56 ` debian developer [this message]
[not found] ` <f24d23310705180409u1cbdcaa1o8302ea05830b75a@mail.gmail.com>
2007-05-18 12:40 ` debian developer
2007-05-18 13:17 ` Greg KH
2007-05-20 8:15 ` [PATCH] Fix duplicated entry in Documentation/HOWTO Junio C Hamano
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=f24d23310705180356p3fd4715p310641d27fb36cbf@mail.gmail.com \
--to=debiandev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®