From: charwhee <charwhee@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: mesa-amber
Date: Wed, 14 Feb 2024 01:51:53 +0100 [thread overview]
Message-ID: <20240214005153.C3A02240BD@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48519@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
New comment by charwhee on void-packages repository
https://github.com/void-linux/void-packages/issues/48519#issuecomment-1942920184
Comment:
Yes, it's for older computers, and Void is one of the only distributions that still support 32-bit architectures, so it makes sense to support older video drivers. If it's not something you want to prioritize, totally understand (I can see all the requests you get). I'll take a crack at it - I suspect it will be identical to mesa except for 'amber' in the name. Cheers!
next prev parent reply other threads:[~2024-02-14 0:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 1:11 [ISSUE] " charwhee
2024-02-12 9:10 ` MIvanchev
2024-02-14 0:51 ` charwhee [this message]
2024-02-14 8:39 ` MIvanchev
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=20240214005153.C3A02240BD@inbox.vuxu.org \
--to=charwhee@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).