From: Jani Nikula <jani.nikula@intel.com>
To: linux-kernel@vger.kernel.org
Cc: jani.nikula@intel.com,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH] MAINTAINERS: clarify that "B:" is the URI where to file bugs
Date: Mon, 5 Dec 2016 14:03:59 +0200 [thread overview]
Message-ID: <1480939439-27947-1-git-send-email-jani.nikula@intel.com> (raw)
Different subsystems and drivers have different preferences for where to
file bugs and what information to include. 686564434e88 ("MAINTAINERS:
Add bug tracking system location entry type") added "B:" entry for this.
Clarify that "B:" specifies the URI for the bug tracker directly, a web
page for detailed info on filing bugs, or a mailto: URI.
Fixes: 686564434e88 ("MAINTAINERS: Add bug tracking system location entry type")
Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
Rafael, I just noticed the "B:" entry popped up in MAINTAINERS from
686564434e88 ("MAINTAINERS: Add bug tracking system location entry
type").
I've been pushing this for some time now, and I'd sent the last patch
adding this before the kernel summit discussion you refer to [1], and
Andrew picked it up, along with the rest in the series. This is where
the whole idea came from!
Specifying "B:" as URI lets subsystems decide whether it contains a bug
tracker or something else.
[1] http://lkml.kernel.org/r/1476966135-26943-1-git-send-email-jani.nikula@intel.com
---
MAINTAINERS | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index f7fd00ef1323..8f55d44b5b26 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -77,7 +77,8 @@ Descriptions of section entries:
Q: Patchwork web based patch tracking system site
T: SCM tree type and location.
Type is one of: git, hg, quilt, stgit, topgit
- B: Bug tracking system location.
+ B: URI for where to file bugs. A web-page with detailed bug
+ filing info, a direct bug tracker link, or a mailto: URI.
S: Status, one of the following:
Supported: Someone is actually paid to look after this.
Maintained: Someone actually looks after it.
--
2.1.4
next reply other threads:[~2016-12-05 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 12:03 Jani Nikula [this message]
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
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=1480939439-27947-1-git-send-email-jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
/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
all inboxes | Powered by JetHome®