From: m3tav3rse <m3tav3rse@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] hex: update to 0.4.1.
Date: Sat, 13 Mar 2021 22:11:32 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29447@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
There is a new pull request by m3tav3rse against master on the void-packages repository
https://github.com/m3tav3rse/void-packages hex
https://github.com/void-linux/void-packages/pull/29447
hex: update to 0.4.1.
A patch file from https://github.com/void-linux/void-packages/pull/29447.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-hex-29447.patch --]
[-- Type: text/x-diff, Size: 941 bytes --]
From ed164d0c3745b1ba10ea0c288cd5fc5b5f56fc94 Mon Sep 17 00:00:00 2001
From: m3tav3rse <mtvrs@tuta.io>
Date: Sat, 13 Mar 2021 22:08:44 +0100
Subject: [PATCH] hex: update to 0.4.1.
---
srcpkgs/hex/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/hex/template b/srcpkgs/hex/template
index 8127d42b2e8..0fcd9618cb8 100644
--- a/srcpkgs/hex/template
+++ b/srcpkgs/hex/template
@@ -1,6 +1,6 @@
# Template file for 'hex'
pkgname=hex
-version=0.3.0
+version=0.4.1
revision=1
build_style=cargo
short_desc="Futuristic take on hexdump"
@@ -8,7 +8,7 @@ maintainer="SolitudeSF <solitudesf@protonmail.com>"
license="MIT"
homepage="https://github.com/sitkevij/hex"
distfiles="${homepage}/archive/v${version}.tar.gz"
-checksum=d929593ae5851c6cb7e778f759fca380245d6053fa3b0cb9643e598a37015c84
+checksum=993c7ab59c98a1b97f348d6609e2ef7cb199f46e85bb06e093a9e01d06d85c97
post_install() {
vlicense LICENSE
next reply other threads:[~2021-03-13 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 21:11 m3tav3rse [this message]
2021-03-13 23:34 ` [PR PATCH] [Merged]: " ericonr
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-29447@inbox.vuxu.org \
--to=m3tav3rse@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).