On Wed, 2007-12-19 at 06:29 -0700, Matthew Wilcox wrote:That's a bit harsh on bugzilla. It is of use to people whose job it is to track outstanding bugs. However, Matthew is completely correct, it's useless for getting bugs fixed *if* the information isn't on the mailing list. The reason for using mailing list is the more eyes principle: if you email linux-scsi, all the SCSI experts will see it, not just the one email listed as owner in bugzilla. Likewise, as the bug goes through analysis, if it turns out to be in a different area, that areas mailing list can be added to the Cc list. So, to get the best of both worlds, file a bugzilla and note the bugid. Then email a complete report to the relevant list, but add [BUG <bugid>] to the subject line and cc bugme-daemon@bugzilla.kernel.org If you do this, bugzilla will keep track of the entire discussion as it progresses and allow those who track bugs through bugzilla to get a pretty accurate idea of the status. You should never need to touch bugzilla again once the initial bug report is filed: all future information flow is via the mailing lists. James --
| Mariusz Kozlowski | [PATCH 01] kmalloc + memset conversion co kzalloc |
| Rafael J. Wysocki | [Bug #10629] 2.6.26-rc1-$sha1: RIP __d_lookup+0x8c/0x160 |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Jeff Garzik | Re: [RFC] Heads up on sys_fallocate() |
git: | |
| Linus Torvalds | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Andrew Morton | Re: [BUG] New Kernel Bugs |
