Github messages for voidlinux
 help / color / mirror / Atom feed
From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] gping: update to 1.6.1.
Date: Thu, 15 Dec 2022 13:44:06 +0100	[thread overview]
Message-ID: <20221215124406.zJj-9wpp5Tk93ZzRV-Lm-LRmAYYobuRqVl9SLeL1DAM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40974@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 473 bytes --]

There is an updated pull request by icp1994 against master on the void-packages repository

https://github.com/icp1994/void-packages gping
https://github.com/void-linux/void-packages/pull/40974

gping: update to 1.6.1.
#### Testing the changes
- I tested the changes in this PR: **briefly**

#### Local build testing
- I built this PR locally for my native architecture, x86_64

A patch file from https://github.com/void-linux/void-packages/pull/40974.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gping-40974.patch --]
[-- Type: text/x-diff, Size: 1032 bytes --]

From fcd9c7ca5b2018ea8de7b9cce11c6146a2ddd607 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Thu, 8 Dec 2022 15:21:47 +0530
Subject: [PATCH] gping: update to 1.6.1.

---
 srcpkgs/gping/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/gping/template b/srcpkgs/gping/template
index ea06e0737fa6..47a6a23168eb 100644
--- a/srcpkgs/gping/template
+++ b/srcpkgs/gping/template
@@ -1,15 +1,15 @@
 # Template file for 'gping'
 pkgname=gping
-version=1.4.0
+version=1.6.1
 revision=1
 build_wrksrc="gping"
 build_style=cargo
 short_desc="Ping, but with a graph"
-maintainer="Paper <paper@tilde.institute>"
+maintainer="icp <pangolin@vivaldi.net>"
 license="MIT"
 homepage="https://github.com/orf/gping/"
 distfiles="https://github.com/orf/gping/archive/refs/tags/gping-v${version}.tar.gz"
-checksum=f68735ee9f6f3fde6881b727c518550d9c486a4259c0a2a2d261971715b77970
+checksum=f27dc8aadd7f323861e8700d47efd13199f924fe0b2e20fef1f537bed01c1454
 
 post_install() {
 	vlicense ../LICENSE

  parent reply	other threads:[~2022-12-15 12:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08  9:54 [PR PATCH] gping: update to 1.5.1 icp1994
2022-12-12  0:40 ` cinerea0
2022-12-12  7:05 ` [PR PATCH] [Updated] " icp1994
2022-12-15  9:24 ` [PR PATCH] [Updated] gping: update to 1.6.0 icp1994
2022-12-15 10:07 ` gping: update to 1.6.1 paper42
2022-12-15 12:43 ` icp1994
2022-12-15 12:44 ` icp1994 [this message]
2022-12-16 18:19 ` [PR PATCH] [Merged]: " paper42

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=20221215124406.zJj-9wpp5Tk93ZzRV-Lm-LRmAYYobuRqVl9SLeL1DAM@z \
    --to=icp1994@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).