From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Filippos Papadopoulos <psybases@gmail.com>,
Boaz Harrosh <bharrosh@panasas.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: INITIO scsi driver fails to work properly
Date: Wed, 19 Dec 2007 10:50:40 -0600 [thread overview]
Message-ID: <1198083040.5487.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20071219132918.GB26272@parisc-linux.org>
On Wed, 2007-12-19 at 06:29 -0700, Matthew Wilcox wrote:
> On Wed, Dec 19, 2007 at 10:48:27AM +0200, Filippos Papadopoulos wrote:
> > Would it be better to open a bug report at bugzilla?
>
> No, it wouldn't. Bugzilla is a place where bug reports go to be
> ignored. Witness 9370 where despite my best efforts to move discussion
> to the mailing list, it's been thoroughly ignored because the original
> reporte insists on posting additional information there instead of to
> the mailing list.
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
next prev parent reply other threads:[~2007-12-19 16:50 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9f00bd9d0712170139q1397af5fp3c855a2b94726227@mail.gmail.com>
2007-12-17 11:18 ` INITIO scsi driver fails to work properly Andrew Morton
2007-12-17 11:41 ` Filippos Papadopoulos
2007-12-17 12:18 ` Boaz Harrosh
2007-12-17 12:24 ` Boaz Harrosh
2007-12-19 8:48 ` Filippos Papadopoulos
2007-12-19 10:08 ` Boaz Harrosh
2007-12-19 13:29 ` Matthew Wilcox
2007-12-19 16:50 ` James Bottomley [this message]
2007-12-19 17:05 ` Matthew Wilcox
2007-12-20 9:32 ` Natalie Protasevich
2007-12-20 15:08 ` James Bottomley
2007-12-20 15:14 ` Theodore Tso
2007-12-21 19:30 ` Chuck Ebbert
2007-12-21 21:03 ` James Bottomley
2007-12-21 22:43 ` Chuck Ebbert
2007-12-21 22:49 ` James Bottomley
2008-01-04 0:18 ` Filippos Papadopoulos
2008-01-11 5:16 ` James Bottomley
2008-01-11 9:54 ` Filippos Papadopoulos
2008-01-11 15:44 ` James Bottomley
2008-01-11 16:44 ` Filippos Papadopoulos
2008-01-11 17:01 ` Alan Cox
2008-01-11 17:33 ` James Bottomley
2008-01-11 17:01 ` James Bottomley
2008-01-13 12:28 ` Filippos Papadopoulos
2008-01-15 15:16 ` James Bottomley
2008-01-16 5:59 ` FUJITA Tomonori
2008-01-16 14:57 ` James Bottomley
2008-01-21 22:20 ` Alan Cox
2008-01-22 17:50 ` Filippos Papadopoulos
2008-01-25 16:49 ` James Bottomley
2008-01-25 21:04 ` Filippos Papadopoulos
2008-01-11 17:52 ` Chuck Ebbert
2008-01-11 18:21 ` Alan Cox
2007-12-17 13:05 ` Alan Cox
2007-12-17 14:40 ` Boaz Harrosh
2007-12-17 14:36 ` Alan Cox
2007-12-17 15:03 ` James Bottomley
2007-12-17 16:08 ` Boaz Harrosh
2007-12-17 16:20 ` Olivier Galibert
2007-12-17 17:00 ` Boaz Harrosh
2007-12-17 16:13 ` Alan Cox
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=1198083040.5487.14.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bharrosh@panasas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=psybases@gmail.com \
/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