From: Jani Nikula <jani.nikula@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] MAINTAINERS: clarify that "B:" is the URI where to file bugs
Date: Thu, 08 Dec 2016 16:55:26 +0200 [thread overview]
Message-ID: <874m2ewjvl.fsf@intel.com> (raw)
In-Reply-To: <15119297.CGM95ee3ZT@aspire.rjw.lan>
On Thu, 08 Dec 2016, "Rafael J. Wysocki" <rjw@rjwysocki.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
next prev parent reply other threads:[~2016-12-08 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 12:03 Jani Nikula
2016-12-06 22:10 ` Rafael J. Wysocki
2016-12-07 8:35 ` Jani Nikula
2016-12-07 23:44 ` Rafael J. Wysocki
2016-12-08 8:55 ` Jani Nikula
2016-12-08 14:26 ` Rafael J. Wysocki
2016-12-08 14:55 ` Jani Nikula [this message]
2016-12-15 7:47 ` Vlastimil Babka
2016-12-15 22:44 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874m2ewjvl.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome