Github messages for voidlinux
 help / color / mirror / Atom feed
From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: mesa: update to version 23.1.5.
Date: Thu, 17 Aug 2023 14:41:42 +0200	[thread overview]
Message-ID: <20230817124142.wAvqRDHmxYAKmnoMFZNfMqsp-X0dPwSphE-IwzihNl0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45542@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]

There's a closed pull request on the void-packages repository

mesa: update to version 23.1.5.
https://github.com/void-linux/void-packages/pull/45542

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **NO(1)**

(1) other people took care of the testing: see here, on the original [PR](https://github.com/void-linux/void-packages/pull/45177).

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


Hey guys, i hope every one is doing great. :smile: 

I'm making this PR to try and bring mesa v23.1.5 to void. Yet i'm aware that my previous PR is still opened, the reason is that i'm away from home (and thus, away from my usual tools i used for previous pr) for a long time, and i don't have the good conditions to do proper tests. So feel free to confirm if this PR works for you ! 

Anyways, a huge thanks to the guys who helped me (did all the work :laughing: ), you guys rock ! :heart: 

Have a great day lads, and take care.
Best regards, Spid

      reply	other threads:[~2023-08-17 12:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 13:43 [PR PATCH] " SpidFightFR
2023-08-17 12:41 ` SpidFightFR [this message]

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=20230817124142.wAvqRDHmxYAKmnoMFZNfMqsp-X0dPwSphE-IwzihNl0@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).