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 08:59:19 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0437903135==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 56F696E6F4 for ; Thu, 30 Oct 2014 01:59:19 -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 --===============0437903135== Content-Type: multipart/alternative; boundary="1414659559.7a3C5f5.31217"; charset="UTF-8" --1414659559.7a3C5f5.31217 Date: Thu, 30 Oct 2014 08:59:19 +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 #208 from Marti Raudsepp --- (In reply to Michel D=C3=A4nzer from comment #207) > In general, it's much better to > track things separately. Once several unrelated issues are mixed up in a > single report, it's very hard to untangle and keep track of it. So *TELL* users that clearly, to make individual bug reports. Close this bu= g if necessary. Direct your users instead of going "oh well, users can't report = bugs and we can't do anything about it". When I was beginning to see these issues, I asked around in #radeon whether= I should report a new bug, and I was told to see this bug instead. Of course = that was another misled user. --=20 You are receiving this mail because: You are the assignee for the bug. --1414659559.7a3C5f5.31217 Date: Thu, 30 Oct 2014 08:59:19 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Comme= nt # 208 on bug 79980<= /a> from = Marti Raudsepp 
(In reply to Michel D=C3=A4nzer from comment #207)
> In general, it's much better to
> track things separately. Once several unrelated issues are mixed up in=
 a
> single report, it's very hard to untangle and keep track of it.

So *TELL* users that clearly, to make individual bug reports. Close this bu=
g if
necessary. Direct your users instead of going "oh well, users can't re=
port bugs
and we can't do anything about it".

When I was beginning to see these issues, I asked around in #radeon whether=
 I
should report a new bug, and I was told to see this bug instead. Of course =
that
was another misled user.

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