From: Joe Perches <joe@perches.com>
To: Dave Gordon <david.s.gordon@intel.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: [Intel-gfx] [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method
Date: Tue, 26 Jan 2016 12:14:04 -0800 [thread overview]
Message-ID: <1453839244.28952.98.camel@perches.com> (raw)
In-Reply-To: <56A791AF.9030804@intel.com>
On Tue, 2016-01-26 at 15:33 +0000, Dave Gordon wrote:
> 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 :)
Thanks Dave. That makes some sense.
get_maintainer could then parse mailto: and http: schemes and
could do the right thing.
prev parent reply other threads:[~2016-01-26 20:14 UTC|newest]
Thread overview: 8+ 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 ` [Intel-gfx] " Dave Gordon
2016-01-26 20:14 ` Joe Perches [this message]
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=1453839244.28952.98.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=david.s.gordon@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.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