From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Bjorn Helgaas <helgaas@kernel.org>, <linux-pci@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: How to improve PCI bug tracking?
Date: Thu, 19 Jan 2017 11:16:48 +0000 [thread overview]
Message-ID: <014be170-8dfc-d0e7-beba-41c66bd6b8da@synopsys.com> (raw)
In-Reply-To: <20170118225332.GA22960@bhelgaas-glaptop.roam.corp.google.com>
Hello,
Às 10:53 PM de 1/18/2017, Bjorn Helgaas escreveu:
> I want to improve PCI bug tracking. It feels like our bugs don't get
> the attention they need, and I'm soliciting ideas for how to improve
> this.
>
> Current situation:
>
> - People often report bugs via email to linux-pci. I think this
> is good because everybody can see it.
>
> - Even after an email report, I often request a bugzilla because
> (1) it helps keep things from being forgotten, (2) it's a
> convenient place to store bulky data, and (3) I like to have a
> bugzilla URL to include in the changelog of a patch that fixes the
> bug.
>
> - Sometimes people open a bugzilla directly. I get email about
> these (along with one or two other people), but this is sort of a
> problem because linux-pci never sees it, sometimes I miss it, and
> things tend to languish.
>
> - Discussion on a bugzilla is only seen by people listed in the
> bugzilla, not on linux-pci.
>
> I'm contemplating changing this so the bugzilla mail would also go to
> linux-pci.
I agree with your approach.
Thanks,
Joao
>
> Any objections or alternate suggestions?
>
> Bjorn
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at https://urldefense.proofpoint.com/v2/url?u=http-3A__vger.kernel.org_majordomo-2Dinfo.html&d=DwIBAg&c=DPL6_X_6JkXFx7AXWqB0tg&r=s2fO0hii0OGNOv9qQy_HRXy-xAJUD1NNoEcc3io_kx0&m=VPUOvpl0WPwnjbNCNU9QIRZYycwLGjHenSFYTNE55aQ&s=-Q0zKU59-QDtodMADouOKavaxZxRqwjeWvMuZ9W1zos&e=
>
prev parent reply other threads:[~2017-01-19 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 22:53 Bjorn Helgaas
2017-01-18 23:29 ` Sinan Kaya
2017-01-19 5:35 ` Lukas Wunner
2017-01-19 11:16 ` Joao Pinto [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=014be170-8dfc-d0e7-beba-41c66bd6b8da@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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
Powered by JetHome