From: mintsuki <mintsuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] limine: update to 4.20230428.0.
Date: Fri, 28 Apr 2023 05:44:28 +0200 [thread overview]
Message-ID: <20230428034428.2TBIZtD7xvV3gLxcV1xx04RdOrPkK5Nq3UwGF8V6lWE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43336@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
There is an updated pull request by mintsuki against master on the void-packages repository
https://github.com/mintsuki/void-packages limine
https://github.com/void-linux/void-packages/pull/43336
limine: update to 4.20230428.0.
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/43336.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-limine-43336.patch --]
[-- Type: text/x-diff, Size: 1087 bytes --]
From 5a4008ccab1a16f7d16d5f8ea28ec9867c168716 Mon Sep 17 00:00:00 2001
From: mintsuki <mintsuki@protonmail.com>
Date: Fri, 28 Apr 2023 05:44:22 +0200
Subject: [PATCH] limine: update to 4.20230428.0.
---
srcpkgs/limine/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/limine/template b/srcpkgs/limine/template
index 06bcf25f033d..1fad25363c8a 100644
--- a/srcpkgs/limine/template
+++ b/srcpkgs/limine/template
@@ -1,6 +1,6 @@
# Template file for 'limine'
pkgname=limine
-version=4.20230330.0
+version=4.20230428.0
revision=1
build_style=gnu-configure
configure_args="--enable-all TOOLCHAIN_FOR_TARGET=llvm"
@@ -10,7 +10,7 @@ maintainer="Mintsuki <mintsuki@protonmail.com>"
license="BSD-2-Clause"
homepage="https://limine-bootloader.org/"
distfiles="https://github.com/limine-bootloader/limine/releases/download/v${version}/limine-${version}.tar.xz"
-checksum=1270145c65adc3933e220ca87a7aaca0e14a5dec18b2821f4ddc9ecdeedbdcb2
+checksum=8771a86769a3405dad729cabceac0a76316964c40dc2f0690398b1e6e01aae41
post_install() {
vlicense LICENSE
next prev parent reply other threads:[~2023-04-28 3:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 2:18 [PR PATCH] limine: update to 4.20230408.0 mintsuki
2023-04-09 15:10 ` biopsin
2023-04-09 19:00 ` mintsuki
2023-04-13 3:56 ` classabbyamp
2023-04-13 7:22 ` biopsin
2023-04-14 12:02 ` [PR PATCH] [Updated] limine: update to 4.20230414.0 mintsuki
2023-04-22 10:41 ` [PR PATCH] [Updated] limine: update to 4.20230422.0 mintsuki
2023-04-28 3:44 ` mintsuki [this message]
2023-05-02 6:58 ` limine: update to 4.20230428.0 mintsuki
2023-05-02 7:42 ` [PR PATCH] [Merged]: " 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=20230428034428.2TBIZtD7xvV3gLxcV1xx04RdOrPkK5Nq3UwGF8V6lWE@z \
--to=mintsuki@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).