Comment # 13
on bug 102885
from Thomas J. Moore
(In reply to Timothy Arceri from comment #11) > Deleting the trace means no one else can investigate the bug. Is this still > a problem? I assumed Samuel Pitoiset already figured out what the problem was, particularly since the git bisect pointed to a change he made. Perhaps you can contact him directly? It's been six months, and multiple releases of Mesa, so I pretty much don't believe this bug will get looked at, and don't care if it gets fixed or not. Testing if it's still broken is already more trouble for me than it's worth. I don't trust dropbox, and have no intention of uploading this file again. (In reply to Timothy Arceri from comment #12) > Possibly a duplicate of bug 105152 Feel free to mark it as such, so I don't have to deal with it any more. It's not the first bug of mine that's been marked as a duplicate of a later bug report. (I didn't read it, but again, I don't care any more). If it's not really a duplicate, feel free to just close this as "won't fix".
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
