Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1317659 > unrolled thread

[PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method

Started byJani Nikula <jani.nikula@intel.com>
First post2016-01-26 10:20 +0100
Last post2016-01-26 21:20 +0100
Articles 8 — 4 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method Jani Nikula <jani.nikula@intel.com> - 2016-01-26 10:20 +0100
    Re: [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method Joe Perches <joe@perches.com> - 2016-01-26 15:40 +0100
    Re: [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method Joe Perches <joe@perches.com> - 2016-01-26 15:50 +0100
      Re: [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method Jani Nikula <jani.nikula@intel.com> - 2016-01-26 16:00 +0100
      Re: [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method Richard Weinberger <richard.weinberger@gmail.com> - 2016-01-26 16:00 +0100
        Re: [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method Jani Nikula <jani.nikula@intel.com> - 2016-01-26 16:10 +0100
      Re: [Intel-gfx] [PATCH v2] MAINTAINERS: Add "B:" preferred bug  reporting method Dave Gordon <david.s.gordon@intel.com> - 2016-01-26 16:40 +0100
        Re: [Intel-gfx] [PATCH v2] MAINTAINERS: Add "B:" preferred bug  reporting method Joe Perches <joe@perches.com> - 2016-01-26 21:20 +0100

#1317659 — [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method

FromJani Nikula <jani.nikula@intel.com>
Date2016-01-26 10:20 +0100
Subject[PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method
Message-ID<qV7X5-1ZG-29@gated-at.bofh.it>
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.

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>

---

v2: drop the B: entry for i915 due to bikeshedding, let's see if there's
a chance this B: entry sticks in general
---
 MAINTAINERS | 2 ++
 1 file changed, 2 insertions(+)

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.
 	T: SCM tree type and location.
 	   Type is one of: git, hg, quilt, stgit, topgit
 	S: Status, one of the following:
-- 
2.1.4

[toc] | [next] | [standalone]


#1317983

FromJoe Perches <joe@perches.com>
Date2016-01-26 15:40 +0100
Message-ID<qVcWM-5sj-55@gated-at.bofh.it>
In reply to#1317659
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.
> 
> 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>
> 
> ---
> 
> v2: drop the B: entry for i915 due to bikeshedding, let's see if
> there's
> a chance this B: entry sticks in general
> ---
>  MAINTAINERS | 2 ++
>  1 file changed, 2 insertions(+)
> 
> 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.
>  	T: SCM tree type and location.
>  	   Type is one of: git, hg, quilt, stgit, topgit
>  	S: Status, one of the following:

[toc] | [prev] | [next] | [standalone]


#1317994

FromJoe Perches <joe@perches.com>
Date2016-01-26 15:50 +0100
Message-ID<qVd6q-5vL-19@gated-at.bofh.it>
In reply to#1317659
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.

[toc] | [prev] | [next] | [standalone]


#1318007

FromJani Nikula <jani.nikula@intel.com>
Date2016-01-26 16:00 +0100
Message-ID<qVdg6-5z6-13@gated-at.bofh.it>
In reply to#1317994
On Tue, 26 Jan 2016, Joe Perches <joe@perches.com> 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.

I meant the word "List" verbatim as a keyword, indicating the bugs
should be reported to the list specified by "L:".

> Maybe there could be something like the "T:" and "S:"
> entries where some additional qualifier is used for the
> specific type of bug reporting.

Maybe we can have a kernel summit session about this, and maybe have a
patch merged by mid-2017.


BR,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center

[toc] | [prev] | [next] | [standalone]


#1318011

FromRichard Weinberger <richard.weinberger@gmail.com>
Date2016-01-26 16:00 +0100
Message-ID<qVdg6-5z6-21@gated-at.bofh.it>
In reply to#1317994
On Tue, Jan 26, 2016 at 3:42 PM, Joe Perches <joe@perches.com> 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.

Yeah, if B: is present, use the given URL for bug reporting.
If not use the mailinglist... :-)

-- 
Thanks,
//richard

[toc] | [prev] | [next] | [standalone]


#1318023

FromJani Nikula <jani.nikula@intel.com>
Date2016-01-26 16:10 +0100
Message-ID<qVdpM-5RZ-11@gated-at.bofh.it>
In reply to#1318011
On Tue, 26 Jan 2016, Richard Weinberger <richard.weinberger@gmail.com> wrote:
> On Tue, Jan 26, 2016 at 3:42 PM, Joe Perches <joe@perches.com> 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.
>
> Yeah, if B: is present, use the given URL for bug reporting.
> If not use the mailinglist... :-)

B: not being present, the status quo, could mean either the list or
https://bugzilla.kernel.org/, depending on the driver/subsystem.

I'd also like to encourage people to add URLs like

https://bugzilla.kernel.org/enter_bug.cgi?product=ACPI&component=BIOS

here to immediately lead the bug reporter to the correct product and
component in the bug tracker.

BR,
Jani.



-- 
Jani Nikula, Intel Open Source Technology Center

[toc] | [prev] | [next] | [standalone]


#1318059 — Re: [Intel-gfx] [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method

FromDave Gordon <david.s.gordon@intel.com>
Date2016-01-26 16:40 +0100
SubjectRe: [Intel-gfx] [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method
Message-ID<qVdSO-644-7@gated-at.bofh.it>
In reply to#1317994
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.

[toc] | [prev] | [next] | [standalone]


#1318335 — Re: [Intel-gfx] [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method

FromJoe Perches <joe@perches.com>
Date2016-01-26 21:20 +0100
SubjectRe: [Intel-gfx] [PATCH v2] MAINTAINERS: Add "B:" preferred bug reporting method
Message-ID<qVifM-QQ-9@gated-at.bofh.it>
In reply to#1318059
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.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web