mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Moffitt <nick@zork.net>
To: Sean Estabrooks <seanlkml@rogers.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [Bug 999] New: Problem with the /dev/ptmx file
Date: Mon, 28 Jul 2003 13:50:57 -0700	[thread overview]
Message-ID: <20030728205057.GB5115@zork.net> (raw)
In-Reply-To: <123101c35544$1b382fb0$7f0a0a0a@lappy7>

begin  Sean Estabrooks  quotation:
> > But if he insists in the crappy bugzilla interface instead of lkml
> > I won't tell him.
[...]
> What's your objection to bugzilla?  It's not perfect but it does
> seem better than the list alone to track a bug.


	    http://bugs.xiph.org/show_bug.cgi?id=245

    Bug systems should make it easy to file, and quick to triage.  The
costs for entering a new bug should be low.  Forcing people to set up
user accounts when NO BUGS WILL EVER BE ASSIGNED TO THEM is just poor
design.  

	Bugzilla is a relic of a system where all the users (including
testers) are employees, and are assumed to have credentials in the
system already.  It does not handle well the zillions of casual bug
detections by end users.  If you've got an in-house QA department, it
may suit them just fine.  Just don't expect every net.random to start
using it and not kvetch gargargar at you when the warts show through.

	Also, the BACK BUTTON for krissakes!

-- 

end
 
 Support your droogs!

  reply	other threads:[~2003-07-28 20:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28 19:39 Martin J. Bligh
2003-07-28 19:55 ` Christoph Hellwig
2003-07-28 20:04   ` Martin J. Bligh
2003-07-28 20:09   ` Sean Estabrooks
2003-07-28 20:50     ` Nick Moffitt [this message]
2003-07-28 20:52     ` Dave Barry
2003-07-29  9:49     ` Christoph Hellwig
2003-07-28 19:40 Martin J. Bligh

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=20030728205057.GB5115@zork.net \
    --to=nick@zork.net \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanlkml@rogers.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

all inboxes | Powered by JetHome®