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:	Tue, 26 Jan 2016 17:05:37 +0200
From:	Jani Nikula <jani.nikula@...el.com>
To:	Richard Weinberger <richard.weinberger@...il.com>,
	Joe Perches <joe@...ches.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	intel-gfx@...ts.freedesktop.org, Daniel Vetter <daniel@...ll.ch>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method

On Tue, 26 Jan 2016, Richard Weinberger <richard.weinberger@...il.com> wrote:
> On Tue, Jan 26, 2016 at 3:42 PM, Joe Perches <joe@...ches.com> wrote:
>> On Tue, 2016-01-26 at 11:10 +0200, Jani Nikula wrote:
>>> Different subsystems and drivers have different preferred ways of
>>> receiving bug reports; mailing list or bugzillas at various
>>> locations. Add "B:" entry for specifying the preference to guide bug
>>> reporters at the right location.
>> []
>>> v2: drop the B: entry for i915 due to bikeshedding, let's see if there's
>>> a chance this B: entry sticks in general
>> []
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 30aca4aa5467..c9da3a2af398 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -75,6 +75,8 @@ Descriptions of section entries:
>>>       L: Mailing list that is relevant to this area
>>>       W: Web-page with status/info
>>>       Q: Patchwork web based patch tracking system site
>>> +     B: Preferred method for reporting bugs; bug tracking system site
>>> +        or "List" for mailing list.
>>
>> I think that "List" is not a good idea.
>>
>> Intermixing mailing list email addresses and URLs seems
>> odd and inconsistent.
>>
>> Maybe there could be something like the "T:" and "S:"
>> entries where some additional qualifier is used for the
>> specific type of bug reporting.
>
> Yeah, if B: is present, use the given URL for bug reporting.
> If not use the mailinglist... :-)

B: not being present, the status quo, could mean either the list or
https://bugzilla.kernel.org/, depending on the driver/subsystem.

I'd also like to encourage people to add URLs like

https://bugzilla.kernel.org/enter_bug.cgi?product=ACPI&component=BIOS

here to immediately lead the bug reporter to the correct product and
component in the bug tracker.

BR,
Jani.



-- 
Jani Nikula, Intel Open Source Technology Center

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ