linux-kernel - Re: [PATCH] MAINTAINERS: clarify that "B:" is the URI where to file bugs

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:   Thu, 08 Dec 2016 16:55:26 +0200
From:   Jani Nikula <jani.nikula@...el.com>
To:     "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc:     linux-kernel@...r.kernel.org,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] MAINTAINERS: clarify that "B:" is the URI where to file bugs

On Thu, 08 Dec 2016, "Rafael J. Wysocki" <rjw@...ysocki.net> wrote:
> And you can even achieve it with the current definition of entires
> like this:
>
> M: <my devel mailing list> (no bug reports please)

I've been told the entries should be machine parseable, without free
form text such as that. Also the reason a URI was deemed the right
choice for "B:", because it doesn't preclude an email address.

> It looks like you are taking what I said as offensive somehow, but
> that was not my intention.  Sorry if it sounded like that.

I'm frustrated and annoyed because I've been trying to get "B:" merged
since the beginning of the year, and there was enough bikeshedding that
I gave up in disgust for months, and now that Andrew picked the stuff up
I thought we had some closure. But no, all that bikeshedding in vain,
something else was merged at rc7 instead.

I don't have the time for this. I hope the bug reporters who'll be told
to report the bugs somewhere else do.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center