From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 79980] Random radeonsi crashes Date: Thu, 30 Oct 2014 03:01:29 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0810827469==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2E8446E695 for ; Wed, 29 Oct 2014 20:01:30 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0810827469== Content-Type: multipart/alternative; boundary="1414638090.5Eae6.14837"; charset="UTF-8" --1414638090.5Eae6.14837 Date: Thu, 30 Oct 2014 03:01:30 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D79980 --- Comment #207 from Michel D=C3=A4nzer --- (In reply to Marti Raudsepp from comment #194) > Shouldn't it be up to the developers to try and make sense of the reports= and > split up the bug entry appropriately? We are doing that all the time. However, users tend to focus too much on so= me symptom(s) they have as well and ignore any differences. It's understandabl= e, but unfortunate. > Should there be one report per affected user, or is there a better way to > group them together? I can't think of anything better than that. In general, it's much better to track things separately. Once several unrelated issues are mixed up in a si= ngle report, it's very hard to untangle and keep track of it. --=20 You are receiving this mail because: You are the assignee for the bug. --1414638090.5Eae6.14837 Date: Thu, 30 Oct 2014 03:01:30 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Comme= nt # 207 on bug 79980<= /a> from Michel D=C3=A4nzer 
(In reply to Marti Raudsepp from comment #194)
> Shouldn't it be up to the developers to try and =
make sense of the reports and
> split up the bug entry appropriately?

We are doing that all the time. However, users tend to focus too much on so=
me
symptom(s) they have as well and ignore any differences. It's understandabl=
e,
but unfortunate.


> Should there be one report per affected user, or=
 is there a better way to
> group them together?

I can't think of anything better than that. In general, it's much better to
track things separately. Once several unrelated issues are mixed up in a si=
ngle
report, it's very hard to untangle and keep track of it.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1414638090.5Eae6.14837-- --===============0810827469== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0810827469==--