From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] mesa: update to 23.1.1.
Date: Mon, 29 May 2023 19:51:10 +0200 [thread overview]
Message-ID: <20230529175110.zSaFmp5vRiU2CCP9bN3oRCJ9SX4S9bV6_0FQyJeYvuA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44108@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
There is an updated pull request by SpidFightFR against master on the void-packages repository
https://github.com/SpidFightFR/void-packages update_mesa
https://github.com/void-linux/void-packages/pull/44108
mesa: update to 23.1.1.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x64-GlibC)
Thanks to Aedinius on the [IRC](https://web.libera.chat/#voidlinux) for helping with this PR !
A patch file from https://github.com/void-linux/void-packages/pull/44108.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update_mesa-44108.patch --]
[-- Type: text/x-diff, Size: 0 bytes --]
next prev parent reply other threads:[~2023-05-29 17:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 21:56 [PR PATCH] mesa: update to 23.1.1. (+ required consul update) SpidFightFR
2023-05-26 21:58 ` [PR PATCH] [Updated] " SpidFightFR
2023-05-27 8:52 ` SpidFightFR
2023-05-27 8:56 ` SpidFightFR
2023-05-27 8:58 ` classabbyamp
2023-05-27 9:07 ` SpidFightFR
2023-05-27 9:42 ` [PR PATCH] [Updated] " SpidFightFR
2023-05-27 9:46 ` SpidFightFR
2023-05-27 13:54 ` mesa: update to 23.1.1 abenson
2023-05-27 14:15 ` abenson
2023-05-27 15:19 ` [PR PATCH] [Updated] " SpidFightFR
2023-05-27 15:20 ` SpidFightFR
2023-05-29 16:24 ` classabbyamp
2023-05-29 17:51 ` SpidFightFR [this message]
2023-05-29 17:51 ` [PR PATCH] [Closed]: " SpidFightFR
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=20230529175110.zSaFmp5vRiU2CCP9bN3oRCJ9SX4S9bV6_0FQyJeYvuA@z \
--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).