Github messages for voidlinux
 help / color / mirror / Atom feed
From: mintsuki <mintsuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] limine: update to 5.20231006.0.
Date: Tue, 24 Oct 2023 19:17:01 +0200	[thread overview]
Message-ID: <20231024171701.MEbnG9rgu_sl77SyDl3qvvpEMyZ69w3uYnvVQ32ArOA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46834@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/46834

limine: update to 5.20231006.0.
#### Testing the changes
- I tested the changes in this PR: **YES**

A patch file from https://github.com/void-linux/void-packages/pull/46834.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-limine-46834.patch --]
[-- Type: text/x-diff, Size: 1089 bytes --]

From 18790ecfa7b71dbc331c7c839bcbaab13e0443b3 Mon Sep 17 00:00:00 2001
From: mintsuki <mintsuki@protonmail.com>
Date: Tue, 24 Oct 2023 19:16:43 +0200
Subject: [PATCH] limine: update to 5.20231024.0.

---
 srcpkgs/limine/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/limine/template b/srcpkgs/limine/template
index efa4b424c726d..8300a8ab0726e 100644
--- a/srcpkgs/limine/template
+++ b/srcpkgs/limine/template
@@ -1,6 +1,6 @@
 # Template file for 'limine'
 pkgname=limine
-version=5.20230917.0
+version=5.20231024.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=2d9b55e798e951ebd3d4266303e9cefda2ee9f7055a3c877dc7e306f0e94ec91
+checksum=87492cb9b129c592da5ccde6d2c754266ddf38faa89bd4686c31bfbd144e229e
 
 post_install() {
 	vlicense LICENSE

  reply	other threads:[~2023-10-24 17:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22 20:13 [PR PATCH] " mintsuki
2023-10-24 17:17 ` mintsuki [this message]
2023-10-28  3:41 ` [PR PATCH] [Updated] limine: update to 5.20231024.0 mintsuki
2023-10-29  3:49 ` [PR PATCH] [Updated] limine: update to 5.20231028.0 mintsuki
2023-11-03  6:47 ` [PR PATCH] [Updated] limine: update to 5.20231029.0 mintsuki
2023-11-03  6:55 ` [PR PATCH] [Updated] limine: update to 5.20231103.0 mintsuki
2023-11-14  8:42 ` mintsuki
2023-11-14 19:21 ` [PR PATCH] [Updated] limine: update to 5.20231114.0 mintsuki
2023-11-21 18:25 ` [PR PATCH] [Updated] limine: update to 5.20231114.1 mintsuki
2023-11-23 19:18 ` limine: update to 5.20231121.0 mintsuki
2023-11-24  2:39 ` [PR PATCH] [Updated] " mintsuki
2023-11-29 16:07 ` [PR PATCH] [Merged]: limine: update to 5.20231124.0 Duncaen
  -- strict thread matches above, loose matches on Subject: below --
2023-09-25  0:10 [PR PATCH] limine: update to 5.20230924.0 mintsuki
2023-10-06 18:04 ` [PR PATCH] [Updated] limine: update to 5.20231006.0 mintsuki
2023-10-08 20:21 ` mintsuki
2023-10-17 23:40 ` mintsuki

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=20231024171701.MEbnG9rgu_sl77SyDl3qvvpEMyZ69w3uYnvVQ32ArOA@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).