Github messages for voidlinux
 help / color / mirror / Atom feed
From: RunningDroid <>
Subject: [PR PATCH] btop: update to 1.2.12.
Date: Fri, 14 Oct 2022 10:26:32 +0200	[thread overview]
Message-ID: <> (raw)

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

There is a new pull request by RunningDroid against master on the void-packages repository update_btop

btop: update to 1.2.12.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

#### New package
- This new package conforms to the [package requirements]( **YES**|**NO**

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl

A patch file from is attached

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

From 810fa42037e4f8b75afd6bbcdd53b232ce629b48 Mon Sep 17 00:00:00 2001
From: RunningDroid <>
Date: Fri, 14 Oct 2022 04:23:46 -0400
Subject: [PATCH] btop: update to 1.2.12.

 srcpkgs/btop/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/btop/template b/srcpkgs/btop/template
index 26dfc427e1c2..34c2800a01e3 100644
--- a/srcpkgs/btop/template
+++ b/srcpkgs/btop/template
@@ -1,6 +1,6 @@
 # Template file for 'btop'
 short_desc="Monitor of resources"
@@ -9,4 +9,4 @@ license="Apache-2.0"

             reply	other threads:[~2022-10-14  8:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  8:26 RunningDroid [this message]
2022-10-14 22:23 ` [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).