From: Theodore Tso <tytso@mit.edu>
To: Natalie Protasevich <protasnb@gmail.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
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: Thu, 20 Dec 2007 10:14:49 -0500 [thread overview]
Message-ID: <20071220151449.GA27081@thunk.org> (raw)
In-Reply-To: <32209efe0712200132k68ba2b40gf6e3a103c216e57@mail.gmail.com>
On Thu, Dec 20, 2007 at 01:32:02AM -0800, Natalie Protasevich wrote:
> > The problem is that it appears to the casual observer as if they can
> > then add information to the bug through the web interface. But that
> > information will never be forwarded to the mailing list. Unless there's
> > a way of marking bugs as 'unchangable through the web interface' or 'all
> > messages appended to this bug need to be forwarded', Bugzilla just
> > doesn't fit our needs.
> >
> > The Debian BTS fits our way of working much better. Perhaps somebody
> > should investigate a migration.
>
> This is excellent observation by Matthew and James. There is no magic
> in bugzilla not being loved, it is just "not the right set of features
> for effective work on a problem". It doesn't support multiple
> developer' collaboration well.
Actually, Bugzilla *could* be configured so that, say, linux-scsi was
copied for all SCSI bugs (linux-scsi could just be added to the cc
list). The problem though is that Bugzilla will then proceed to cc
linux-scsi for all the Bugzilla state change details which might annoy
the denizens of the linux-scsi list.
But if new entries on the Bugzilla entry could be set to forward to
the appropriate mailing list with the messaging *looking* a lot more
like a mail message, I suspect it could be acceptable. One of the
advantages of the Debian BTS is that it's much more integrated into
the e-mail workflow. (Although it lacks the roll up and reporting
capabilities that are beloved by managers...)
But hey, it could be worse. We could have chosen the Sourceforge bug
tracker. :-)
- Ted
next prev parent reply other threads:[~2007-12-20 15:15 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
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 [this message]
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=20071220151449.GA27081@thunk.org \
--to=tytso@mit.edu \
--cc=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=protasnb@gmail.com \
--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