From: Takashi Iwai <tiwai@suse.de>
To: Jani Nikula <jani.nikula@intel.com>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug reporting feedback loop
Date: Wed, 28 Jun 2017 15:13:52 +0200 [thread overview]
Message-ID: <s5h4lv0jlv3.wl-tiwai@suse.de> (raw)
In-Reply-To: <87shikb6iq.fsf@intel.com>
On Wed, 28 Jun 2017 15:12:29 +0200,
Jani Nikula wrote:
>
> On Thu, 22 Jun 2017, Takashi Iwai <tiwai@suse.de> wrote:
> > On Thu, 22 Jun 2017 16:12:09 +0200,
> > Jiri Kosina wrote:
> >>
> >> On Thu, 22 Jun 2017, Takashi Iwai wrote:
> >>
> >> > - The inconsistent bug tracking over the whole kernel areas:
> >> > which way to report purely depends on the subsystem. Even inside a
> >> > subsystem, some prefer bugzilla while some don't.
> >>
> >> Agreed that this might be annoying for the reporters, but I don't think we
> >> want to go towards pushing maintainers to use one unified solution. That'd
> >> be counter-productive.
> >
> > I don't pursue that, either. It'd be great, though, if we can reduce
> > the too much differences. The variety is the strength of open source,
> > but in this case...
>
> The least we can do is use the MAINTAINERS "B:" tag to document the
> preferences of each subsystem or driver.
Yes. There are way too few entries for "B:" right now.
Takashi
next prev parent reply other threads:[~2017-06-28 13:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 22:34 [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug reporting feedback loop Laura Abbott
2017-06-22 12:36 ` Jiri Kosina
2017-06-27 17:53 ` Luis R. Rodriguez
2017-06-27 18:26 ` Laurent Pinchart
2017-06-27 18:30 ` James Bottomley
2017-06-27 18:41 ` Daniel Vetter
2017-06-27 19:02 ` Luis R. Rodriguez
2017-06-27 19:46 ` Guenter Roeck
2017-06-28 10:19 ` Mark Brown
2017-06-27 22:35 ` Jiri Kosina
2017-06-28 6:59 ` Takashi Iwai
2017-06-27 18:31 ` Takashi Iwai
2017-06-27 19:04 ` Luis R. Rodriguez
2017-06-28 8:04 ` Daniel Vetter
2017-06-22 14:08 ` Takashi Iwai
2017-06-22 14:12 ` Jiri Kosina
2017-06-22 14:24 ` Takashi Iwai
2017-06-28 13:12 ` Jani Nikula
2017-06-28 13:13 ` Takashi Iwai [this message]
2017-06-22 15:34 ` James Bottomley
2017-06-23 14:52 ` Greg KH
2017-06-23 20:28 ` Jiri Kosina
2017-06-25 17:11 ` Laura Abbott
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=s5h4lv0jlv3.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=jani.nikula@intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).