From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110729] Broken links on Linux Man Pages
Date: Wed, 22 May 2019 14:25:20 +0000 [thread overview]
Message-ID: <bug-110729-502-hBor1vACfv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110729-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1095 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110729
Eric Engestrom <fdo-bugs@engestrom.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Product|Mesa |DRI
Version|19.1 |unspecified
Component|Other |libdrm
QA Contact|mesa-dev@lists.freedesktop. |
|org |
Assignee|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop
|org |.org
--- Comment #1 from Eric Engestrom <fdo-bugs@engestrom.ch> ---
We have no control over that website :)
Beside, this is a libdrm issue, not Mesa, so reassigning.
The actual issue is that not enough documentation has been written, including
several (most) functions that have none.
This is something that we've known for a while but haven't dealt with yet.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2796 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next parent reply other threads:[~2019-05-22 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-110729-502@http.bugs.freedesktop.org/>
2019-05-22 14:25 ` bugzilla-daemon [this message]
2019-09-24 17:09 ` [Bug 110729] Broken links on Linux Man Pages 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-110729-502-hBor1vACfv@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