From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mesa: update to 23.1.1.
Date: Wed, 31 May 2023 01:52:29 +0200 [thread overview]
Message-ID: <20230530235229.Dchw3BaaVH4lGwQM5ITK92QL8bI-6uQkZoE5twzjRNw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44138@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
New comment by JamiKettunen on void-packages repository
https://github.com/void-linux/void-packages/pull/44138#issuecomment-1569289563
Comment:
There was no need to make a new PR replacing #44108 as you can always just amend/force-push to update the state of the branch; I guess this also supersedes #42407.
Anyway this definitely should be tested on `musl` with a modern AMD GPU as on Chimera Linux my RX 6600 was having some heavy artifacts on 23.1.x while rebuilding 23.0.3 got rid of it, I'll start bisecting this and may be able to supply a patch or something later as needed.
next prev parent reply other threads:[~2023-05-30 23:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 18:46 [PR PATCH] " SpidFightFR
2023-05-30 23:52 ` JamiKettunen [this message]
2023-05-31 12:41 ` SpidFightFR
2023-06-01 18:39 ` JamiKettunen
2023-06-07 18:11 ` SpidFightFR
2023-06-08 22:29 ` HadetTheUndying
2023-06-10 21:26 ` JamiKettunen
2023-06-14 17:26 ` [PR PATCH] [Merged]: " Duncaen
-- strict thread matches above, loose matches on Subject: below --
2023-05-26 21:56 [PR PATCH] mesa: update to 23.1.1. (+ required consul update) SpidFightFR
2023-05-27 13:54 ` mesa: update to 23.1.1 abenson
2023-05-27 14:15 ` abenson
2023-05-27 15:20 ` SpidFightFR
2023-05-29 16:24 ` 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=20230530235229.Dchw3BaaVH4lGwQM5ITK92QL8bI-6uQkZoE5twzjRNw@z \
--to=jamikettunen@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).