public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@intel.com>
Cc: linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, daniel@ffwll.ch,
	airlied@gmail.com, joe@perches.com, akpm@linux-foundation.org
Subject: Re: [PATCH 1/4] MAINTAINERS: Add "B:" for URI where to file bugs
Date: Mon, 24 Oct 2016 10:31:29 +0200	[thread overview]
Message-ID: <20161024083129.GD20761@phenom.ffwll.local> (raw)
In-Reply-To: <1476966135-26943-1-git-send-email-jani.nikula@intel.com>

On Thu, Oct 20, 2016 at 03:22:12PM +0300, Jani Nikula wrote:
> Different subsystems and drivers have different preferences for where to
> file bugs and what information to include. Add "B:" entry for specifying
> the URI for the bug tracker directly, a web page for detailed info on
> filing bugs, or a mailto: URI.
> 
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Cc: Joe Perches <joe@perches.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> 
> ---
> 
> Dust settled since the last time, maybe we can make URI work?

fwiw I want this, I think documenting bugzilla and irc channels (for
subsystems and drivers using them) will help a lot to make
(sub)communities of the kernel more approachable. On the entire series:

Very-much-Wanted-by: Daniel Vetter <daniel.vetter@ffwll.ch>

> ---
>  MAINTAINERS | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 89112a65b831..4a47ec00a09d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -74,6 +74,8 @@ Descriptions of section entries:
>  	   These reviewers should be CCed on patches.
>  	L: Mailing list that is relevant to this area
>  	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.
>  	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
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  parent reply	other threads:[~2016-10-24  8:31 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 ` [PATCH 3/4] MAINTAINERS: Add "C:" for URI for chat where developers hang out Jani Nikula
2016-10-20 12:22 ` [PATCH 4/4] MAINTAINERS: add drm and drm/i915 irc channels Jani Nikula
2016-10-24  8:31 ` Daniel Vetter [this message]
2016-10-24  8:48 ` [PATCH 1/4] MAINTAINERS: Add "B:" for URI where to file bugs 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=20161024083129.GD20761@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --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