ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Joerg Roedel <joro@8bytes.org>,
	Thorsten Leemhuis <regressions@leemhuis.info>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Regression tracking
Date: Tue, 09 Aug 2016 16:20:02 -0700	[thread overview]
Message-ID: <1470784802.2299.85.camel@HansenPartnership.com> (raw)
In-Reply-To: <20160809223118.GG1437@8bytes.org>

On Wed, 2016-08-10 at 00:31 +0200, Joerg Roedel wrote:
> On Tue, Aug 09, 2016 at 09:02:22PM +0200, Thorsten Leemhuis wrote:
> > Yeah, definitely. One afaics important part that needs to be done 
> > in this area: make bugzilla.kernel.org work better. At least some 
> > (or maybe even quite a lot?) of the bugs reported there afaics seem 
> > to not get proper attention from the right people. Due to that I'd 
> > assume some testers will have come to conclusions like "testing for 
> > regressions and bugs is not worth the trouble, as the kernel 
> > developers are not interested in the bugs I file anyway".
> 
> In my case, I am only looking into the kernel.org bugzilla if someone
> pings me about it. Usually I get the upstream bug reports via email.


You can have bugzilla.kernel.org configured to send your list email
when someone reports a new bug.

It used to actually be useful: you could reply and it would capture
that in the bugzilla entry.  However, since the migration to bugzilla
version 3, this has started to fail, so you need to add the reporter's
cc directly as well now.

Once you get this configuration set up it means that bugzilla and email
can be directly equivalent, it's just that only email will have the
complete bug text (because bugzilla is lossy on the replies).

James

  parent reply	other threads:[~2016-08-09 23:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 14:31 Takashi Iwai
2016-07-26 20:36 ` Rafael J. Wysocki
2016-07-27 12:28   ` Thorsten Leemhuis
2016-08-01 19:58     ` Thorsten Leemhuis
2016-08-09  9:40     ` Joerg Roedel
2016-08-09 19:02       ` Thorsten Leemhuis
2016-08-09 20:21         ` Takashi Iwai
2016-08-09 22:31         ` Joerg Roedel
2016-08-09 22:55           ` Rafael J. Wysocki
2016-08-09 23:20           ` James Bottomley [this message]
2016-08-10 15:11             ` Joerg Roedel
2016-08-10 12:03           ` Jani Nikula
2016-08-10 15:01             ` Joerg Roedel
2016-08-10 16:19               ` Daniel Vetter
2016-08-10 16:47         ` 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=1470784802.2299.85.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=joro@8bytes.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=regressions@leemhuis.info \
    /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