lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Fri, 18 May 2007 16:26:28 +0530
From:	"debian developer" <debiandev@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Fwd: [BUG] HOWTO

---------- Forwarded message ----------
From: debian developer <debiandev@...il.com>
Date: May 18, 2007 4:24 PM
Subject: [BUG] HOWTO
To: greg@...ah.com, linux-kernel@...r.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ