From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: xorg-server: needs libxshmfence-devel
Date: Fri, 12 Nov 2021 13:12:11 +0100 [thread overview]
Message-ID: <20211112121211.v5nQX7TiNhhAMiqIS98GqNrk2MN4l6s58AArslrIDIw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34043@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 285 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/34043#issuecomment-967065232
Comment:
I wonder if this wouldn't fit inside mesa devel deps as well... There are packages that might have fallback code paths or whatever for its lack.
next prev parent reply other threads:[~2021-11-12 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 11:53 [PR PATCH] " newbluemoon
2021-11-12 12:12 ` ericonr [this message]
2021-11-12 20:03 ` q66
2021-11-12 20:10 ` [PR PATCH] [Updated] " newbluemoon
2021-11-12 20:11 ` newbluemoon
2021-11-12 20:18 ` [PR PATCH] [Merged]: " q66
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=20211112121211.v5nQX7TiNhhAMiqIS98GqNrk2MN4l6s58AArslrIDIw@z \
--to=ericonr@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).