From: Jani Nikula <jani.nikula@intel.com>
To: linux-kernel@vger.kernel.org
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
daniel@ffwll.ch, airlied@gmail.com, joe@perches.com,
akpm@linux-foundation.org, Jani Nikula <jani.nikula@intel.com>
Subject: [PATCH 3/4] MAINTAINERS: Add "C:" for URI for chat where developers hang out
Date: Thu, 20 Oct 2016 15:22:14 +0300 [thread overview]
Message-ID: <1476966135-26943-3-git-send-email-jani.nikula@intel.com> (raw)
In-Reply-To: <1476966135-26943-1-git-send-email-jani.nikula@intel.com>
Make it easier to find the developer chat for the subsystem or driver.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 689f7f08a100..53df9ccc5573 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -76,6 +76,8 @@ Descriptions of section entries:
W: Web-page with status/info
B: URI for where to file bugs. A web-page with detailed bug
filing info, a direct bug tracker link, or a mailto: URI.
+ C: URI for chat protocol, server and channel where developers
+ usually hang out, for example irc://server/channel.
Q: Patchwork web based patch tracking system site
T: SCM tree type and location.
Type is one of: git, hg, quilt, stgit, topgit
--
2.1.4
next prev parent reply other threads:[~2016-10-20 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 12:22 [PATCH 1/4] MAINTAINERS: Add "B:" for URI where to file bugs Jani Nikula
2016-10-20 12:22 ` [PATCH 2/4] MAINTAINERS: add drm and drm/i915 bug filing info Jani Nikula
2016-10-20 12:22 ` Jani Nikula [this message]
2016-10-20 12:22 ` [PATCH 4/4] MAINTAINERS: add drm and drm/i915 irc channels Jani Nikula
2016-10-24 8:31 ` [PATCH 1/4] MAINTAINERS: Add "B:" for URI where to file bugs Daniel Vetter
2016-10-24 8:48 ` Andrew Donnellan
2016-10-24 18:05 ` [RFC PATCH] get_maintainer: Look for arbitrary letter prefixes in sections Joe Perches
2016-11-03 9:07 ` Paul Bolle
2016-11-03 9:16 ` Joe Perches
2016-11-03 9:18 ` Paul Bolle
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=1476966135-26943-3-git-send-email-jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
/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®