From: HadetTheUndying <HadetTheUndying@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mesa: update to 23.0.3.
Date: Thu, 04 May 2023 19:57:41 +0200 [thread overview]
Message-ID: <20230504175741.P25VBCwdSS8fgkxDAGoi-BEM1dGChKCgm2rpIhhI-Ws@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42407@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
New comment by HadetTheUndying on void-packages repository
https://github.com/void-linux/void-packages/pull/42407#issuecomment-1535185463
Comment:
Just an update I've tested this PR on all of my machines including my Steam Deck without issues now so I'm pretty certain there are no issues with the PR that aren't already being tracked in the upstream.
next prev parent reply other threads:[~2023-05-04 17:57 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 9:49 [PR PATCH] [NOMERGE] mesa: update to 23.0.0 ardadem
2023-04-01 12:05 ` [PR PATCH] [Updated] " ardadem
2023-04-01 12:29 ` tranzystorek-io
2023-04-01 12:30 ` tranzystorek-io
2023-04-01 12:33 ` [PR PATCH] [Updated] " ardadem
2023-04-01 12:35 ` ardadem
2023-04-03 11:05 ` [PR PATCH] [Updated] mesa: update to 23.0.1 ardadem
2023-04-03 11:06 ` ardadem
2023-04-08 14:33 ` ardadem
2023-04-08 14:35 ` ardadem
2023-04-14 20:18 ` [PR PATCH] [Updated] mesa: update to 23.0.2 ardadem
2023-04-17 17:42 ` [PR REVIEW] " mhmdanas
2023-04-18 6:58 ` [PR PATCH] [Updated] " ardadem
2023-04-18 7:00 ` ardadem
2023-04-18 7:02 ` [PR REVIEW] " ardadem
2023-04-18 8:32 ` mhmdanas
2023-04-18 8:34 ` mhmdanas
2023-04-18 8:40 ` mhmdanas
2023-04-25 7:13 ` HadetTheUndying
2023-04-25 7:15 ` HadetTheUndying
2023-04-25 16:34 ` baal-zebub
2023-04-25 18:54 ` JamiKettunen
2023-04-27 16:24 ` [PR PATCH] [Updated] " ardadem
2023-04-29 17:59 ` mesa: update to 23.0.3 zlice
2023-04-29 18:00 ` zlice
2023-04-29 19:27 ` HadetTheUndying
2023-04-30 21:54 ` kenrap
2023-05-04 17:57 ` HadetTheUndying [this message]
2023-05-11 5:49 ` kenrap
2023-05-16 15:34 ` Mek101
2023-05-17 9:05 ` biopsin
2023-05-18 4:10 ` HadetTheUndying
2023-05-19 5:41 ` saltnpepper97
2023-05-19 5:45 ` saltnpepper97
2023-05-19 6:13 ` saltnpepper97
2023-05-19 7:22 ` JamiKettunen
2023-05-19 8:40 ` saltnpepper97
2023-05-19 8:53 ` saltnpepper97
2023-05-19 15:01 ` mhmdanas
2023-05-19 19:00 ` saltnpepper97
2023-05-19 19:49 ` saltnpepper97
2023-05-19 19:52 ` HadetTheUndying
2023-05-19 21:27 ` SpidFightFR
2023-05-20 1:02 ` saltnpepper97
2023-05-25 21:51 ` HadetTheUndying
2023-06-02 18:09 ` ardadem
2023-06-02 18:09 ` [PR PATCH] [Closed]: " ardadem
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=20230504175741.P25VBCwdSS8fgkxDAGoi-BEM1dGChKCgm2rpIhhI-Ws@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).