From: Dave Gordon <david.s.gordon@intel.com>
To: Joe Perches <joe@perches.com>,
Jani Nikula <jani.nikula@intel.com>,
linux-kernel@vger.kernel.org
Cc: intel-gfx@lists.freedesktop.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method
Date: Tue, 26 Jan 2016 15:33:03 +0000 [thread overview]
Message-ID: <56A791AF.9030804@intel.com> (raw)
In-Reply-To: <1453819327.28952.93.camel@perches.com>
On 26/01/16 14:42, Joe Perches wrote:
> On Tue, 2016-01-26 at 11:10 +0200, Jani Nikula wrote:
>> Different subsystems and drivers have different preferred ways of
>> receiving bug reports; mailing list or bugzillas at various
>> locations. Add "B:" entry for specifying the preference to guide bug
>> reporters at the right location.
> []
>> v2: drop the B: entry for i915 due to bikeshedding, let's see if there's
>> a chance this B: entry sticks in general
> []
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 30aca4aa5467..c9da3a2af398 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -75,6 +75,8 @@ Descriptions of section entries:
>> L: Mailing list that is relevant to this area
>> W: Web-page with status/info
>> Q: Patchwork web based patch tracking system site
>> + B: Preferred method for reporting bugs; bug tracking system site
>> + or "List" for mailing list.
>
> I think that "List" is not a good idea.
>
> Intermixing mailing list email addresses and URLs seems
> odd and inconsistent.
>
> Maybe there could be something like the "T:" and "S:"
> entries where some additional qualifier is used for the
> specific type of bug reporting.
Make it a proper URI, allowing mailto:<listname@domain>
or http://bugzilla.org/i915/ or anything else that people
may come up with in future :)
.Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-01-26 15:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 9:10 [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method Jani Nikula
2016-01-26 14:36 ` Joe Perches
2016-01-26 14:42 ` Joe Perches
2016-01-26 14:49 ` Richard Weinberger
2016-01-26 15:05 ` Jani Nikula
2016-01-26 14:55 ` Jani Nikula
2016-01-26 15:33 ` Dave Gordon [this message]
2016-01-26 20:14 ` Joe Perches
2016-01-27 16:47 ` ✗ Fi.CI.BAT: failure for MAINTAINERS: Add "B:" preferred bug reporting method (rev3) Patchwork
2016-01-27 17:16 ` Joe Perches
2016-01-27 17:38 ` Damien Lespiau
2016-01-27 17:03 ` ✓ Fi.CI.BAT: success " Patchwork
2016-01-28 14:06 ` Patchwork
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=56A791AF.9030804@intel.com \
--to=david.s.gordon@intel.com \
--cc=akpm@linux-foundation.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