From: HadetTheUndying <HadetTheUndying@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mesa: update to 21.2.4.
Date: Fri, 15 Oct 2021 21:49:52 +0200 [thread overview]
Message-ID: <20211015194952.LpOmHXVKfjqm5GRLRuUbN16Qfi1m7QKm7zUkiyM2xao@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33546@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
New comment by HadetTheUndying on void-packages repository
https://github.com/void-linux/void-packages/pull/33546#issuecomment-944620000
Comment:
> Out of curiosity and not related to the PR it self, why are all ex. mesa-dri-${version}/lib/dri/*.so files equal, could we not symlink them all to one common mesa_dri.so ?
Definitely out of scope for this PR. Also beyond me. 21.3.0 is in RC phase now maybe bring that up in a PR for the next major release upgrade.
next prev parent reply other threads:[~2021-10-15 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 20:32 [PR PATCH] " HadetTheUndying
2021-10-14 21:45 ` biopsin
2021-10-15 19:49 ` HadetTheUndying [this message]
2021-10-17 22:37 ` [PR PATCH] [Merged]: " paper42
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=20211015194952.LpOmHXVKfjqm5GRLRuUbN16Qfi1m7QKm7zUkiyM2xao@z \
--to=hadettheundying@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).