From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] vifm: update to 0.11.
Date: Mon, 28 Sep 2020 23:44:42 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25168@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
There is a new pull request by ailiop-git against master on the void-packages repository
https://github.com/ailiop-git/void-packages vifm
https://github.com/void-linux/void-packages/pull/25168
vifm: update to 0.11.
A patch file from https://github.com/void-linux/void-packages/pull/25168.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-vifm-25168.patch --]
[-- Type: text/x-diff, Size: 951 bytes --]
From 6a0b3eb90d9ec6e4803657e534a9abc1b4b26c11 Mon Sep 17 00:00:00 2001
From: Anthony Iliopoulos <ailiop@altatus.com>
Date: Mon, 28 Sep 2020 23:41:22 +0200
Subject: [PATCH] vifm: update to 0.11.
---
srcpkgs/vifm/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/vifm/template b/srcpkgs/vifm/template
index 557585589cd..a6d632d27e3 100644
--- a/srcpkgs/vifm/template
+++ b/srcpkgs/vifm/template
@@ -1,6 +1,6 @@
# Template file for 'vifm'
pkgname=vifm
-version=0.10.1
+version=0.11
revision=1
build_style=gnu-configure
configure_args="--without-gtk"
@@ -12,7 +12,7 @@ maintainer="Alessio Sergi <al3hex@gmail.com>"
license="GPL-2.0-or-later"
homepage="https://vifm.info/"
distfiles="${SOURCEFORGE_SITE}/vifm/vifm-${version}.tar.bz2"
-checksum=99006f56db05e1bdfb7983e8d5c31c9ac93bf2ac9e0409a577c8ca660fecd03b
+checksum=d06f7e25f1ba0936f27f3d34401cc9eaa50ccc5a5e70ad5659e5014f04691e67
CFLAGS="-fcommon"
next reply other threads:[~2020-09-28 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 21:44 ailiop-git [this message]
2020-09-29 1:16 ` [PR PATCH] [Merged]: " 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-25168@inbox.vuxu.org \
--to=ailiop-git@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).