From: bra1nwave <bra1nwave@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] inxi: update to 3.1.04.
Date: Fri, 03 Jul 2020 14:58:44 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23378@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
There is a new pull request by bra1nwave against master on the void-packages repository
https://github.com/bra1nwave/void-packages inxi
https://github.com/void-linux/void-packages/pull/23378
inxi: update to 3.1.04.
A patch file from https://github.com/void-linux/void-packages/pull/23378.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-inxi-23378.patch --]
[-- Type: text/x-diff, Size: 993 bytes --]
From 35465272a5826d5fb383e1c4382119d3c8d4d9eb Mon Sep 17 00:00:00 2001
From: bra1nwave <bra1nwave@protonmail.com>
Date: Fri, 3 Jul 2020 14:58:17 +0200
Subject: [PATCH] inxi: update to 3.1.04.
---
srcpkgs/inxi/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/inxi/template b/srcpkgs/inxi/template
index 84c5e915b0c..4126ef12968 100644
--- a/srcpkgs/inxi/template
+++ b/srcpkgs/inxi/template
@@ -1,6 +1,6 @@
# Template file for 'inxi'
pkgname=inxi
-version=3.1.03
+version=3.1.04
revision=1
archs=noarch
wrksrc="inxi-${version}-1"
@@ -12,7 +12,7 @@ license="GPL-3.0-or-later"
homepage="https://smxi.org/docs/inxi.htm"
changelog="https://raw.githubusercontent.com/smxi/inxi/master/inxi.changelog"
distfiles="https://github.com/smxi/inxi/archive/${version}-1.tar.gz"
-checksum=af6843ee886a95e7e35cec8ffb2877b9c9b7b11ed4e9a129fab66b07a536d2a9
+checksum=9661ee7120a5bdc5b7cd0b36a56aa18924283490e5430216d2ed8dc685cfc68c
do_install() {
vbin inxi
next reply other threads:[~2020-07-03 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 12:58 bra1nwave [this message]
2020-07-03 18:39 ` [PR PATCH] [Merged]: " Chocimier
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23378@inbox.vuxu.org \
--to=bra1nwave@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).