From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-process/btop/
Date: Sun, 15 Jan 2023 20:34:38 +0000 (UTC) [thread overview]
Message-ID: <1673814867.5decab50d095c66a9ea974fe96aee1a4f497de02.sam@gentoo> (raw)
commit: 5decab50d095c66a9ea974fe96aee1a4f497de02
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 15 20:34:27 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Jan 15 20:34:27 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5decab50
sys-process/btop: Stabilize 1.2.13-r1 x86, #890935
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-process/btop/btop-1.2.13-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-process/btop/btop-1.2.13-r1.ebuild b/sys-process/btop/btop-1.2.13-r1.ebuild
index 4819e97cbf06..06313d6fcf82 100644
--- a/sys-process/btop/btop-1.2.13-r1.ebuild
+++ b/sys-process/btop/btop-1.2.13-r1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/aristocratos/btop/archive/refs/tags/v${PV}.tar.gz ->
LICENSE="Apache-2.0"
SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~ppc ppc64 ~riscv ~x86"
+KEYWORDS="~amd64 ~arm64 ~ppc ppc64 ~riscv x86"
BDEPEND="
>=sys-devel/gcc-8
next reply other threads:[~2023-01-15 20:34 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 20:34 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-10 18:38 [gentoo-commits] repo/gentoo:master commit in: sys-process/btop/ James Le Cuirot
2024-11-10 0:43 Jakov Smolić
2024-11-09 9:02 Arthur Zamarin
2024-11-09 9:02 Arthur Zamarin
2024-11-05 20:43 Sam James
2024-11-05 20:43 Sam James
2024-11-05 10:31 Florian Schmaus
2024-03-23 13:39 Sam James
2024-03-23 10:41 Michał Górny
2024-03-23 10:25 Michał Górny
2024-03-02 14:08 Arthur Zamarin
2024-02-21 2:15 Sam James
2024-02-21 2:15 Sam James
2024-02-21 1:48 Sam James
2024-02-18 12:44 Yixun Lan
2024-01-29 6:38 WANG Xuerui
2023-12-11 8:29 Florian Schmaus
2023-07-26 3:35 Sam James
2023-07-26 3:35 Sam James
2023-07-26 3:35 Sam James
2023-07-26 0:55 Sam James
2023-06-27 8:07 James Le Cuirot
2023-03-23 0:43 Sam James
2023-02-24 17:15 Arthur Zamarin
2023-01-15 20:39 Sam James
2023-01-15 20:34 Sam James
2023-01-15 20:27 Arthur Zamarin
2022-12-10 13:10 Joonas Niilola
2022-12-09 15:36 Sam James
2022-12-09 13:55 Arthur Zamarin
2022-12-09 13:55 Arthur Zamarin
2022-12-09 13:39 Arthur Zamarin
2022-11-18 13:07 Arthur Zamarin
2022-11-10 5:20 Sam James
2022-11-10 5:20 Sam James
2022-11-10 5:20 Sam James
2022-11-10 5:11 Arthur Zamarin
2022-11-07 11:33 Florian Schmaus
2022-10-10 11:49 Sam James
2022-10-09 8:55 Agostino Sarubbo
2022-10-09 8:48 Agostino Sarubbo
2022-10-08 19:54 Arthur Zamarin
2022-10-08 16:32 Arthur Zamarin
2022-10-07 21:07 Florian Schmaus
2022-09-15 12:48 Sam James
2022-09-07 6:34 Florian Schmaus
2022-09-07 6:34 Florian Schmaus
2022-08-24 13:57 Yixun Lan
2022-08-12 6:58 Joonas Niilola
2022-08-12 6:58 Joonas Niilola
2022-08-12 4:49 Arthur Zamarin
2022-08-12 4:49 Arthur Zamarin
2022-07-05 7:09 Joonas Niilola
2022-07-05 6:45 Agostino Sarubbo
2022-07-05 6:04 Agostino Sarubbo
2022-07-05 6:02 Agostino Sarubbo
2022-07-04 13:57 Florian Schmaus
2022-06-18 7:18 Ulrich Müller
2022-06-05 12:47 Jakov Smolić
2022-06-04 10:44 Jakov Smolić
2022-06-04 8:19 Florian Schmaus
2022-06-03 10:51 Florian Schmaus
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=1673814867.5decab50d095c66a9ea974fe96aee1a4f497de02.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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