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] [day] [month] [year] [list]
Date:	Fri, 28 Oct 2011 11:44:09 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	maciej.rutecki@...il.com, Florian Mickler <florian@...kler.org>,
	linux-kernel@...r.kernel.org
Subject: Re: regression tracking

On Thu, Oct 27, 2011 at 2:35 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> On Wednesday, October 26, 2011, Maciej Rutecki wrote:
>> Hi
>>
>> On środa, 26 października 2011 o 19:23:11 Bjorn Helgaas wrote:
>> > The regression tracking that you folks used to do before the demise of
>> > bugzilla.kernel.org was incredibly valuable.
>> >
>> > I'm very concerned about the fact that we don't have a systematic way
>> > to do this any more.  Some things do get reported on LKML, of course,
>> > but without the legwork you guys did, I'm afraid we're just dropping
>> > things on the floor because there's no summary of what the issues are,
>> > how many people are seeing them, who's responsible, etc.
>> >
>> > Consider this as (1) kudos for performing an essential community
>> > service, and (2) a plea for the resurrection or replacement of
>> > bugzilla.kernel.org or some other mechanism for reviving regression
>> > tracking.
>>
>> Because bugzilla is still down, I yesterday started send regressions (found in
>> LKML) report directly to Rafael, to create summary report (etc.) of them.
>> Until bugzilla comes back, we plan to collect regression in this way, but any
>> proposal for a better solution is welcome.
>
> Seconded.
>
> Especially if there's a password-protected Wiki service somewhere that we
> could use to store data temporarily until the BZ is back, it would be much
> appreciated.

I don't know exactly what you would like to do with a wiki, but Google
Docs might be a possibility.

Disclaimer: I work for Google but this is not any sort of official
offer of help or support beyond the standard functionality that's
available to everybody.

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