From: bra1nwave <bra1nwave@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] cheat: update to 4.1.0.
Date: Sat, 17 Oct 2020 09:03:41 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25673@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 310 bytes --]
There is a new pull request by bra1nwave against master on the void-packages repository
https://github.com/bra1nwave/void-packages cheat
https://github.com/void-linux/void-packages/pull/25673
cheat: update to 4.1.0.
A patch file from https://github.com/void-linux/void-packages/pull/25673.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cheat-25673.patch --]
[-- Type: text/x-diff, Size: 971 bytes --]
From 71f35afb9a1f52da3ed84ea0c448312135e5de73 Mon Sep 17 00:00:00 2001
From: bra1nwave <bra1nwave@protonmail.com>
Date: Sat, 17 Oct 2020 09:03:01 +0200
Subject: [PATCH] cheat: update to 4.1.0.
---
srcpkgs/cheat/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/cheat/template b/srcpkgs/cheat/template
index b3020476f47..af2daed5856 100644
--- a/srcpkgs/cheat/template
+++ b/srcpkgs/cheat/template
@@ -1,6 +1,6 @@
# Template file for 'cheat'
pkgname=cheat
-version=4.0.2
+version=4.1.0
revision=1
build_style=go
go_import_path="github.com/cheat/cheat/cmd/cheat"
@@ -9,7 +9,7 @@ maintainer="bra1nwave <bra1nwave@protonmail.com>"
license="MIT"
homepage="https://github.com/cheat/cheat"
distfiles="${homepage}/archive/${version}.tar.gz"
-checksum=87c832b25794d7acac2fa4bd3389c81819535f32242d5e99284da76a1a86f1f3
+checksum=b392c3a77eda61f4b1f0991cb30c6202f74472713293e73f645fb697665ca72c
post_install() {
vman doc/cheat.1
next reply other threads:[~2020-10-17 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 7:03 bra1nwave [this message]
2020-10-20 18:20 ` [PR PATCH] [Closed]: " ahesford
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-25673@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).