[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB60836F8B9E045C5542D01ADAFC569@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Fri, 30 Sep 2022 17:28:35 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: "Bird, Tim" <Tim.Bird@...y.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Thorsten Leemhuis <linux@...mhuis.info>
CC: Slade Watkins <srw@...dewatkins.net>,
"Artem S. Tashkinov" <aros@....com>,
Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
"workflows@...r.kernel.org" <workflows@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Torvalds, Linus" <torvalds@...ux-foundation.org>,
"regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
"ksummit@...ts.linux.dev" <ksummit@...ts.linux.dev>
Subject: RE: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla
blues"
> E-mails sent from a web interface could have as much structure as you'd like.
> So one avenue would be to set up a nice interface for bug reporting, that just
> delivered the form data in e-mail format to the proposed bug-receiving mail list.
Web interfaces have the advantage that they can be full of boxes which indicate
useful details to supply. Like what kernel version? Did this work on an older version,
is so, which one? Which CPU vendor/model are you using? Is there an error message?
Are there warnings in the console log before the error? Can you upload a full console log?
Does this happen repeatably? What are the steps to reproduce?
Etc.etc.
Sometimes it takes a few round trips by e-mail to establish the baseline facts.
-Tony
Powered by blists - more mailing lists