From: zen0bit <zen0bit@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] btop: Update to 1.3.0
Date: Mon, 08 Jan 2024 01:05:41 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48113@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
There is a new pull request by zen0bit against master on the void-packages repository
https://github.com/oSoWoSo/VUR btop
https://github.com/void-linux/void-packages/pull/48113
btop: Update to 1.3.0
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x64 glibc)
A patch file from https://github.com/void-linux/void-packages/pull/48113.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-btop-48113.patch --]
[-- Type: text/x-diff, Size: 991 bytes --]
From 65791d188a71f2cccfc355e093592c08e48a040b Mon Sep 17 00:00:00 2001
From: zenobit <zen@osowoso.xyz>
Date: Mon, 8 Jan 2024 01:04:22 +0100
Subject: [PATCH] btop: Update to 1.3.0
---
srcpkgs/btop/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/btop/template b/srcpkgs/btop/template
index 46b60b18611ae..ffd64997e06ac 100644
--- a/srcpkgs/btop/template
+++ b/srcpkgs/btop/template
@@ -1,6 +1,6 @@
# Template file for 'btop'
pkgname=btop
-version=1.2.13
+version=1.3.0
revision=1
build_style=gnu-makefile
short_desc="Monitor of resources"
@@ -9,4 +9,4 @@ license="Apache-2.0"
homepage="https://github.com/aristocratos/btop"
changelog="https://raw.githubusercontent.com/aristocratos/btop/main/CHANGELOG.md"
distfiles="https://github.com/aristocratos/btop/archive/refs/tags/v${version}.tar.gz"
-checksum=668dc4782432564c35ad0d32748f972248cc5c5448c9009faeb3445282920e02
+checksum=375e078ce2091969f0cd14030620bd1a94987451cf7a73859127a786006a32cf
next reply other threads:[~2024-01-08 0:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 0:05 zen0bit [this message]
2024-01-08 0:46 ` Calandracas606
2024-01-08 0:48 ` Calandracas606
2024-01-10 2:41 ` [PR PATCH] [Updated] " zen0bit
2024-02-15 16:00 ` mdkcore0
2024-02-15 16:51 ` [PR PATCH] [Updated] " zen0bit
2024-02-15 17:57 ` btop: Update to 1.3.2 Calandracas606
2024-02-15 18:06 ` zen0bit
2024-02-15 18:13 ` Calandracas606
2024-02-15 18:14 ` zen0bit
2024-02-15 18:20 ` Calandracas606
2024-02-15 19:08 ` Calandracas606
2024-02-15 19:43 ` Calandracas606
2024-02-15 20:14 ` zen0bit
2024-02-15 20:15 ` zen0bit
2024-02-15 21:14 ` zen0bit
2024-02-15 21:21 ` cinerea0
2024-02-15 21:36 ` Calandracas606
2024-02-15 22:46 ` Calandracas606
2024-03-28 1:30 ` dm17
2024-03-28 1:30 ` dm17
2024-03-28 2:18 ` Calandracas606
2024-03-28 10:23 ` [PR PATCH] [Updated] " zen0bit
2024-06-17 3:47 ` [PR PATCH] [Merged]: " classabbyamp
2024-02-05 5:47 [PR PATCH] btop: update to 1.3.0 caughtquick
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-48113@inbox.vuxu.org \
--to=zen0bit@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).