From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-process/bottom/
Date: Wed, 1 Sep 2021 07:53:53 +0000 (UTC) [thread overview]
Message-ID: <1630482830.c6c472d4e9a57cd3be0931449c3067aba41059de.ago@gentoo> (raw)
commit: c6c472d4e9a57cd3be0931449c3067aba41059de
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Wed Sep 1 07:53:50 2021 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Wed Sep 1 07:53:50 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c6c472d4
sys-process/bottom: amd64 stable wrt bug #811297
Package-Manager: Portage-3.0.20, Repoman-3.0.2
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
sys-process/bottom/bottom-0.6.3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-process/bottom/bottom-0.6.3.ebuild b/sys-process/bottom/bottom-0.6.3.ebuild
index 559b1158b09..d7cd1e64b7a 100644
--- a/sys-process/bottom/bottom-0.6.3.ebuild
+++ b/sys-process/bottom/bottom-0.6.3.ebuild
@@ -181,7 +181,7 @@ SRC_URI="$(cargo_crate_uris)"
LICENSE="Apache-2.0 Apache-2.0-with-LLVM-exceptions BSD BSD-2 MIT MPL-2.0 Unlicense ZLIB"
SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~ppc64"
+KEYWORDS="amd64 ~arm64 ~ppc64"
# Rust packages ignore CFLAGS and LDFLAGS so let's silence the QA warnings
QA_FLAGS_IGNORED="usr/bin/btm"
next reply other threads:[~2021-09-01 7:53 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 7:53 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-04 7:54 [gentoo-commits] repo/gentoo:master commit in: sys-process/bottom/ Florian Schmaus
2024-10-04 7:54 Florian Schmaus
2024-09-11 22:13 Sam James
2024-09-09 20:44 Arthur Zamarin
2024-09-08 6:42 Sam James
2024-08-03 15:51 Michał Górny
2024-01-11 13:33 Joonas Niilola
2023-10-26 18:24 Arthur Zamarin
2023-10-18 6:29 Joonas Niilola
2023-09-11 23:54 Sam James
2023-09-11 22:59 Sam James
2023-09-11 22:59 Sam James
2023-09-11 12:24 Florian Schmaus
2023-07-13 9:17 Florian Schmaus
2023-07-13 9:17 Florian Schmaus
2023-07-13 9:17 Florian Schmaus
2023-07-13 9:17 Florian Schmaus
2023-07-02 17:31 Sam James
2023-07-02 8:33 Sam James
2023-07-02 8:04 Sam James
2023-05-27 7:49 Joonas Niilola
2023-05-16 14:02 Florian Schmaus
2023-05-16 14:02 Florian Schmaus
2023-04-18 13:10 Joonas Niilola
2023-03-31 16:37 Sam James
2023-03-31 16:23 Sam James
2023-03-31 16:22 Arthur Zamarin
2023-02-26 7:53 Joonas Niilola
2023-02-26 7:53 Joonas Niilola
2023-02-26 7:53 Joonas Niilola
2023-02-12 2:05 Sam James
2023-02-12 2:05 Sam James
2023-02-11 19:13 Sam James
2023-01-10 7:51 Florian Schmaus
2023-01-06 9:15 Florian Schmaus
2023-01-06 9:15 Florian Schmaus
2022-03-12 16:55 Arthur Zamarin
2022-03-12 13:51 Arthur Zamarin
2022-03-12 6:11 Joonas Niilola
2022-02-10 4:01 Ionen Wolkens
2022-02-02 0:10 Sam James
2022-02-02 0:10 Sam James
2022-02-01 7:30 Agostino Sarubbo
2021-12-30 8:39 Florian Schmaus
2021-12-30 8:39 Florian Schmaus
2021-10-20 0:22 Sam James
2021-10-18 23:50 Sam James
2021-10-18 23:49 Sam James
2021-09-04 21:39 Sam James
2021-09-01 7:55 Agostino Sarubbo
2021-07-24 5:42 Georgy Yakovlev
2021-07-24 5:42 Georgy Yakovlev
2021-07-24 5:42 Georgy Yakovlev
2021-07-24 5:42 Georgy Yakovlev
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=1630482830.c6c472d4e9a57cd3be0931449c3067aba41059de.ago@gentoo \
--to=ago@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