All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107990] Got Dying Light working in Arch by changing Mesa's compile steps, how to get it working Out Of the Box?
Date: Thu, 31 Jan 2019 10:45:12 +0000	[thread overview]
Message-ID: <bug-107990-502-kaBVP65b8B@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107990-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 434 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107990

--- Comment #10 from John <john.ettedgui@gmail.com> ---
Hey Timothy,

is this something fairly easy to get into for someone with no knowledge of
OpenGL or Mesa (I've had a patch 5 years ago, so pretty much the same as no
knowledge)? If so, unless John wants to do it, I would be willing to try.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1322 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

  parent reply	other threads:[~2019-01-31 10:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 14:25 [Bug 107990] Got Dying Light working in Arch by changing Mesa's compile steps, how to get it working Out Of the Box? bugzilla-daemon
2018-09-19 23:13 ` bugzilla-daemon
2018-09-20  2:50 ` bugzilla-daemon
2018-09-20  4:12 ` bugzilla-daemon
2018-09-28  1:03 ` bugzilla-daemon
2018-10-18 23:32 ` bugzilla-daemon
2018-11-29  4:21 ` bugzilla-daemon
2019-01-12 22:38 ` bugzilla-daemon
2019-01-19 19:29 ` bugzilla-daemon
2019-01-31  8:26 ` bugzilla-daemon
2019-01-31 10:45 ` bugzilla-daemon [this message]
2019-02-01 12:09 ` bugzilla-daemon
2019-06-29  1:42 ` bugzilla-daemon
2019-07-01 16:35 ` 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-107990-502-kaBVP65b8B@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.