From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99850] Tessellation bug on Carrizo
Date: Thu, 23 Feb 2017 01:20:18 +0000 [thread overview]
Message-ID: <bug-99850-502-FTsStLoZHK@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99850-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 786 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99850
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|RESOLVED |REOPENED
--- Comment #10 from Michel Dänzer <michel@daenzer.net> ---
Bug reports should only be resolved once the fix has landed in Git, preferably
with a reference to the commit fixing it.
BTW, always specify explicit Git commit hashes instead of "HEAD". HEAD refers
to the currently checked out commit, it has no meaning outside of your local
repository.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2188 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:[~2017-02-23 1:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 15:32 [Bug 99850] Tessellation bug on Carrizo bugzilla-daemon
2017-02-17 15:33 ` bugzilla-daemon
2017-02-17 17:53 ` bugzilla-daemon
2017-02-20 5:58 ` bugzilla-daemon
2017-02-22 17:11 ` bugzilla-daemon
2017-02-22 17:14 ` bugzilla-daemon
2017-02-22 17:15 ` bugzilla-daemon
2017-02-22 17:20 ` bugzilla-daemon
2017-02-22 17:28 ` bugzilla-daemon
2017-02-22 18:14 ` bugzilla-daemon
2017-02-23 1:20 ` bugzilla-daemon [this message]
2017-02-23 10:34 ` bugzilla-daemon
2017-02-28 15:50 ` 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-99850-502-FTsStLoZHK@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;
as well as URLs for NNTP newsgroup(s).