From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] riff: update to 2.18.0.
Date: Fri, 22 Jul 2022 06:15:49 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38183@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
There is a new pull request by 0x5c against master on the void-packages repository
https://github.com/0x5c/void-packages update-riff
https://github.com/void-linux/void-packages/pull/38183
riff: update to 2.18.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/38183.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-riff-38183.patch --]
[-- Type: text/x-diff, Size: 982 bytes --]
From 9b9388c560ed29b90fb268fc54dce7346ed1f6f5 Mon Sep 17 00:00:00 2001
From: 0x5c <dev@0x5c.io>
Date: Fri, 22 Jul 2022 00:14:37 -0400
Subject: [PATCH] riff: update to 2.18.0.
---
srcpkgs/riff/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/riff/template b/srcpkgs/riff/template
index b449c6dcc147..602561a6a79f 100644
--- a/srcpkgs/riff/template
+++ b/srcpkgs/riff/template
@@ -1,6 +1,6 @@
# Template file for 'riff'
pkgname=riff
-version=2.17.0
+version=2.18.0
revision=1
build_style=cargo
short_desc="Diff filter highlighting which line parts have changed"
@@ -8,7 +8,7 @@ maintainer="0x5c <dev@0x5c.io>"
license="MIT"
homepage="https://github.com/walles/riff"
distfiles="https://github.com/walles/riff/archive/refs/tags/${version}.tar.gz"
-checksum=8153c3b1b91a550dcc97925cc257c846d6a7e36408d5c1f229f392983cf4c8a6
+checksum=a4f86f128a287af44c4c1da0e474b4e187afcef780ed2672bec4d3d592353d71
post_install() {
vlicense LICENSE
next reply other threads:[~2022-07-22 4:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 4:15 0x5c [this message]
2022-07-22 4:59 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38183@inbox.vuxu.org \
--to=0x5c@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).