From: Joerg Roedel <joro@8bytes.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Regression tracking
Date: Wed, 10 Aug 2016 17:11:34 +0200 [thread overview]
Message-ID: <20160810151134.GI1437@8bytes.org> (raw)
In-Reply-To: <1470784802.2299.85.camel@HansenPartnership.com>
On Tue, Aug 09, 2016 at 04:20:02PM -0700, James Bottomley wrote:
> 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).
That would be start, at least. For my case, there is not even an IOMMU
category yet, I'll try to open a bug to change that and see what
happens :)
Joerg
next prev parent reply other threads:[~2016-08-10 15:11 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
2016-08-10 15:11 ` Joerg Roedel [this message]
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=20160810151134.GI1437@8bytes.org \
--to=joro@8bytes.org \
--cc=James.Bottomley@HansenPartnership.com \
--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