From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: ol: update to 2.4.
Date: Wed, 08 Mar 2023 16:50:39 +0100 [thread overview]
Message-ID: <20230308155039.yTDX8yxPs5fjjvfAxAQI-v8rss4oF_Pw_l3NK0Ii7vQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42590@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]
There's a merged pull request on the void-packages repository
ol: update to 2.4.
https://github.com/void-linux/void-packages/pull/42590
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built and tested this PR locally for my native architecture, **x86_64**
- I built and tested (using **proot** and **qemu**) this PR locally for these architectures:
- :heavy_check_mark: x86_64, :heavy_check_mark: x86_64-musl
- :heavy_check_mark: aarch64, :heavy_check_mark: aarch64-musl
- :heavy_check_mark: armv5te, :heavy_check_mark: armv5te-musl
- :heavy_check_mark: armv5tel, :heavy_check_mark: armv5tel-musl
- :heavy_check_mark: armv6l, :heavy_check_mark: armv6l-musl
- :heavy_check_mark: armv6hf, :heavy_check_mark: armv6hf-musl
- :heavy_check_mark: armv7l, :heavy_check_mark: armv7l-musl
- :heavy_check_mark: armv7hf, :heavy_check_mark: armv7hf-musl
- :heavy_check_mark: i686, :heavy_check_mark: i686-musl
- :heavy_check_mark: mips-musl, :heavy_check_mark: mipsel-musl, :heavy_check_mark: mipshf-musl, :heavy_check_mark: mipselhf-musl
- :heavy_check_mark: ppc64, :heavy_check_mark: ppc64-musl
- :heavy_check_mark: ppc64le, :heavy_check_mark: ppc64le-musl
- :heavy_check_mark: ppc, :heavy_check_mark: ppc-musl
- :heavy_minus_sign: ppcle, :heavy_minus_sign: ppcle-musl
prev parent reply other threads:[~2023-03-08 15:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 21:20 [PR PATCH] " yuriy-chumak
2023-03-04 22:26 ` [PR PATCH] [Updated] " yuriy-chumak
2023-03-04 23:45 ` yuriy-chumak
2023-03-05 1:16 ` yuriy-chumak
2023-03-05 1:31 ` yuriy-chumak
2023-03-05 1:36 ` yuriy-chumak
2023-03-05 1:45 ` yuriy-chumak
2023-03-05 2:08 ` yuriy-chumak
2023-03-05 2:22 ` yuriy-chumak
2023-03-05 19:54 ` [PR REVIEW] " icp1994
2023-03-05 19:54 ` icp1994
2023-03-05 19:54 ` icp1994
2023-03-06 16:32 ` yuriy-chumak
2023-03-06 16:42 ` [PR PATCH] [Updated] " yuriy-chumak
2023-03-06 16:46 ` [PR REVIEW] " yuriy-chumak
2023-03-06 17:10 ` [PR PATCH] [Updated] " yuriy-chumak
2023-03-06 17:42 ` [PR REVIEW] " classabbyamp
2023-03-06 17:50 ` yuriy-chumak
2023-03-06 17:51 ` yuriy-chumak
2023-03-06 17:56 ` yuriy-chumak
2023-03-06 17:58 ` yuriy-chumak
2023-03-06 18:06 ` yuriy-chumak
2023-03-06 18:37 ` classabbyamp
2023-03-06 20:25 ` yuriy-chumak
2023-03-06 20:33 ` [PR PATCH] [Updated] " yuriy-chumak
2023-03-06 20:39 ` [PR REVIEW] " yuriy-chumak
2023-03-06 21:05 ` yuriy-chumak
2023-03-08 15:50 ` leahneukirchen [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=20230308155039.yTDX8yxPs5fjjvfAxAQI-v8rss4oF_Pw_l3NK0Ii7vQ@z \
--to=leahneukirchen@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).