From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mesa: update to 24.2.3
Date: Wed, 18 Sep 2024 20:47:11 +0200 [thread overview]
Message-ID: <20240918184711.A9C5F2FC97@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51881@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
New comment by SpidFightFR on void-packages repository
https://github.com/void-linux/void-packages/pull/51881#issuecomment-2359161232
Comment:
#### Testing the changes
- I tested the changes in this PR: ~~briefly~~ **YES** (EDIT: on bare metal)
#### Local build testing
- I built this PR locally for my native architecture, (x64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- x64-musl
Please, may we have a review for mesa 24.2.3? We are 1 major version behind upstream and missing many performance patches...
There was no news on this front for quite some time, do i need to do something in particular that i missed ?
Please ping me if so i'd gladly help.
next prev parent reply other threads:[~2024-09-18 18:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 19:50 [PR PATCH] mesa: update to 24.2.0 SpidFightFR
2024-08-16 19:51 ` SpidFightFR
2024-08-16 19:51 ` SpidFightFR
2024-08-17 4:40 ` classabbyamp
2024-08-17 7:58 ` SpidFightFR
2024-08-17 8:13 ` [PR PATCH] [Updated] " SpidFightFR
2024-08-17 8:55 ` SpidFightFR
2024-08-29 19:28 ` [PR PATCH] [Updated] " SpidFightFR
2024-08-29 19:28 ` mesa: update to 24.2.1 SpidFightFR
2024-09-06 20:03 ` [PR PATCH] [Updated] " SpidFightFR
2024-09-07 7:41 ` biopsin
2024-09-07 8:21 ` SpidFightFR
2024-09-07 8:23 ` SpidFightFR
2024-09-07 8:26 ` SpidFightFR
2024-09-08 10:17 ` mesa: update to 24.2.2 SpidFightFR
2024-09-18 18:35 ` [PR PATCH] [Updated] " SpidFightFR
2024-09-18 18:38 ` SpidFightFR
2024-09-18 18:47 ` SpidFightFR [this message]
2024-09-29 3:01 ` [PR PATCH] [Merged]: mesa: update to 24.2.3 classabbyamp
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=20240918184711.A9C5F2FC97@inbox.vuxu.org \
--to=spidfightfr@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).