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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d9def9db0704281558r57460a6ft76bbddcc480058eb@mail.gmail.com>
Date:	Sun, 29 Apr 2007 00:58:09 +0200
From:	"Markus Rechberger" <mrechberger@...il.com>
To:	"Linus Torvalds" <torvalds@...ux-foundation.org>
Cc:	"Adrian Bunk" <bunk@...sta.de>,
	"Diego Calleja" <diegocg@...il.com>,
	"Chuck Ebbert" <cebbert@...hat.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.21

On 4/29/07, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>
>
> On Sat, 28 Apr 2007, Adrian Bunk wrote:
> >
> > We are already quite good at ignoring bug reports that come through
> > linux-kernel, and it's an _advantage_ of the kernel Bugzilla to see more
> > than 1600 open bugs because this tells how bad we are at handling bugs.
>
> No, it just shows that bugzilla doesn't matter for most of the kernel.
>
> Don't say that "bugzilla tells how bad we are at handling bugs". It tells
> how bad *bugzilla* is for handling bugs, nothing more.
>

I totally disagree here, bugzilla is a very good tool. If someone is
too lazy to look at it it's his problem.
Kernel Janitors can pick out some bugs which aren't addressed by
anyone or got left behind. I also found some bugs there which could
have been solved by anyone here, the matter is just that many people
aren't interested in mainly bug fixing and many also work on different
other topics here.

How else should bugs get handled, sending them to the lkml?
I'm 100% sure some bugreports will also get lost then, but on the lkml
they'll very likely remain lost whereas in the bugzilla they'll remain
as open.

> Trying to play politics by pointing to bugzilla is pointless. Bugzilla is
> used for a few subsystems (ACPI seems to use it actively, for example),
> but I doubt most developers use it.
>

as for the em28xx I actively use it, but I also set up a mailinglist
etc. and there are many supporters already...

> Would be be good to have a better bug-tracking setup? Yes. But I think it
> takes man-power, and it would take something *fundamentally* better than
> bugzilla.
>

what are your suggestions to improve a bugreporting tool, I'm very
sure that many people, especially people who want to get into existing
projects here, would love to contribute.

> Maybe the new "http://kernelnewbies.org/known_regressions" thing will
> evolve to something worth tracking. Right now, bugzilla isn't it (although
> it can be a useful tracking place for individual bugs, *once* you've found
> and gotten the right developer involved - but that's a huge step that
> bugzilla generally does *not* do for us).
>

I'd say this is a personal opinion, some people will get along with it
and some of them will not...

Markus
-
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