From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gcovr: update to 4.2
Date: Sun, 10 Nov 2019 03:33:38 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16290@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 303 bytes --]
There is a new pull request by ndowens against master on the void-packages repository
https://github.com/ndowens/void-packages gcovr
https://github.com/void-linux/void-packages/pull/16290
gcovr: update to 4.2
A patch file from https://github.com/void-linux/void-packages/pull/16290.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gcovr-16290.patch --]
[-- Type: text/x-diff, Size: 958 bytes --]
From 174c64a2db986b8b6e5fb775f3dfe67c5a0f467f Mon Sep 17 00:00:00 2001
From: Nathan Owens <ndowens04@gmail.com>
Date: Sat, 9 Nov 2019 20:21:26 -0600
Subject: [PATCH] gcovr: update to 4.2
---
srcpkgs/gcovr/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/gcovr/template b/srcpkgs/gcovr/template
index 2b9ff94bf2a..1a4aa009700 100644
--- a/srcpkgs/gcovr/template
+++ b/srcpkgs/gcovr/template
@@ -1,6 +1,6 @@
# Template file for 'gcovr'
pkgname=gcovr
-version=4.1
+version=4.2
revision=1
archs=noarch
build_style=python3-module
@@ -12,7 +12,7 @@ maintainer="Andre Klitzing <aklitzing@gmail.com>"
license="BSD-3-Clause"
homepage="https://gcovr.com/"
distfiles="https://github.com/gcovr/gcovr/archive/${version}.tar.gz"
-checksum=1ad8042fd4dc4c355fd7e605d395eefa2a59b1677dfdc308e0ef00083e8b37ee
+checksum=589d5cb7164c285192ed0837d3cc17001ba25211e24933f0ba7cb9cf38b8a30e
post_install() {
vlicense LICENSE.txt
next reply other threads:[~2019-11-10 2:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 2:33 voidlinux-github [this message]
2019-11-10 9:52 ` [PR PATCH] [Merged]: " voidlinux-github
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-16290@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).