linux-kernel - Re: kernel bugzilla is FPOS (was: Re: "buggy cmd640" message followed by soft lockup)

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]

Date:	Mon, 26 Nov 2007 22:45:55 +0100
From:	Adrian Bunk <bunk@...nel.org>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Natalie Protasevich <protasnb@...il.com>
Subject: Re: kernel bugzilla is FPOS (was: Re: "buggy cmd640" message
	followed by soft lockup)

On Mon, Nov 26, 2007 at 01:30:06AM +0100, Rafael J. Wysocki wrote:
> On Monday, 26 of November 2007, Adrian Bunk wrote:
>...
> > That's not possible, but as already said it's not required.
> > And more important, it's unrelated to any problems we have.
> > 
> > And it sounds funny that you first write specifications mandating stuff 
> > like "IMO, first, it should ask for what the bug is against" and then 
> > demand an additional email interface that bypasses everything you 
> > demanded previously.
> 
> I just realize that there are people who wouldn't like to use the web interface
> and would prefer to use email instead.

In the cases where these are kernel developers that do (or should) 
handle dozens of bugs each week I see a point if they have problems 
integrating some medium into their workflow.

But in all software, no matter whether open source or commercial, bug 
reporters simply have to use whatever the vendor offers as support 
channel.

> Moreover, you won't force people to use the web interface only for reporting
> bugs, because frankly for some kinds of problems it's too heavywieght

That developers who know what they are doing might bypass the bug
tracking is not a problem.

> (compilation problems and purely software, reproducible things like that are
> much faster resolved using email; this also applies to easily reproducible bugs
> in general).  Still, it wouldn't hurt if they were automatically tracked.

This sounds like "a bit pregnant"...

Tracking requires things like e.g. categorizing the issue and marking it 
as fixed when it got fixed.

> > > Also, if you "switch to email", and then want to switch back to the web
> > > interface, the Cc list from the email messages will be lost.
> > 
> > The perfect is the enemy of the good.
> 
> Sure.
> 
> Greetings,
> Rafael

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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