From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97022] Garbage in windows while running a game windowed
Date: Sun, 31 Jul 2016 20:49:00 +0000 [thread overview]
Message-ID: <bug-97022-502-cjAf4mU7vZ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97022-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 517 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97022
--- Comment #11 from Chernovsky Oleg <adonai@xaker.ru> ---
No, I was asking Michael actually, but thanks for explanation, it guves a clue.
Regression is a situation when something was working before update and stopped
afterwards. So in your case in Mesa 11 it worked and broke in Mesa 12. Most
likely something was broken between releases, that's why Michael asked for
bisect.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1296 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-07-31 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 13:19 [Bug 97022] Garbage in windows while running a game windowed bugzilla-daemon
2016-07-21 13:58 ` bugzilla-daemon
2016-07-21 13:59 ` bugzilla-daemon
2016-07-22 1:56 ` bugzilla-daemon
2016-07-22 9:38 ` bugzilla-daemon
2016-07-22 15:39 ` bugzilla-daemon
2016-07-22 15:40 ` bugzilla-daemon
2016-07-22 15:41 ` bugzilla-daemon
2016-07-22 19:43 ` bugzilla-daemon
2016-07-30 10:21 ` bugzilla-daemon
2016-07-30 14:33 ` bugzilla-daemon
2016-07-31 20:49 ` bugzilla-daemon [this message]
2016-08-09 0:09 ` bugzilla-daemon
2016-08-09 12:02 ` bugzilla-daemon
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=bug-97022-502-cjAf4mU7vZ@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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