From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-process/atop/
Date: Wed, 15 Nov 2017 22:42:35 +0000 (UTC) [thread overview]
Message-ID: <1510785750.e8e17dfd4183ebdadee86189bdf36ac78ea34e89.slyfox@gentoo> (raw)
commit: e8e17dfd4183ebdadee86189bdf36ac78ea34e89
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 15 22:40:24 2017 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Wed Nov 15 22:42:30 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e8e17dfd
sys-process/atop: stable 2.3.0-r1 for hppa, bug #590466
Package-Manager: Portage-2.3.14, Repoman-2.3.6
RepoMan-Options: --include-arches="hppa"
sys-process/atop/atop-2.3.0-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-process/atop/atop-2.3.0-r1.ebuild b/sys-process/atop/atop-2.3.0-r1.ebuild
index 8808312a623..e0a0640ed94 100644
--- a/sys-process/atop/atop-2.3.0-r1.ebuild
+++ b/sys-process/atop/atop-2.3.0-r1.ebuild
@@ -16,7 +16,7 @@ SRC_URI+=" https://github.com/Atoptool/atop/commit/5f101e656a24271726d1e9cd67263
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~hppa ~mips ppc ~ppc64 x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha amd64 ~arm hppa ~mips ppc ~ppc64 x86 ~amd64-linux ~x86-linux"
IUSE=""
RDEPEND="
next reply other threads:[~2017-11-15 22:42 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 22:42 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-03 19:24 [gentoo-commits] repo/gentoo:master commit in: sys-process/atop/ Arthur Zamarin
2025-04-03 15:48 Sam James
2025-04-03 15:48 Sam James
2025-04-03 15:48 Sam James
2025-04-01 0:31 Sam James
2025-03-31 20:55 Sam James
2025-03-20 8:35 Arthur Zamarin
2025-02-16 12:11 Sam James
2024-10-10 11:04 Arthur Zamarin
2024-10-08 21:50 Jakov Smolić
2024-10-05 14:30 Arthur Zamarin
2024-10-05 12:02 Arthur Zamarin
2024-08-11 21:14 Sam James
2024-08-11 20:56 Sam James
2024-03-02 16:31 Arthur Zamarin
2024-02-18 20:02 Arthur Zamarin
2024-02-18 20:02 Arthur Zamarin
2024-02-18 19:57 Arthur Zamarin
2024-01-14 3:46 Sam James
2024-01-14 3:40 Sam James
2023-11-27 11:23 Sam James
2023-08-02 8:17 Sam James
2023-07-24 21:02 Sam James
2023-07-24 13:39 Arthur Zamarin
2023-07-15 8:45 Arthur Zamarin
2023-05-20 7:02 Sam James
2023-05-03 18:58 Sam James
2023-03-04 11:03 Arthur Zamarin
2023-03-04 7:04 Arthur Zamarin
2023-01-08 5:20 Sam James
2023-01-08 5:20 Sam James
2022-12-31 23:28 Sam James
2022-10-29 21:39 Sam James
2022-04-17 17:12 Sam James
2022-02-20 5:27 Sam James
2022-02-19 6:29 Arthur Zamarin
2022-02-19 6:29 Arthur Zamarin
2022-02-19 6:29 Arthur Zamarin
2022-02-19 3:02 Sam James
2022-01-13 5:33 Sam James
2022-01-09 8:05 Sam James
2022-01-09 1:06 Sam James
2022-01-07 5:14 Sam James
2021-12-20 7:36 Sam James
2021-10-11 13:47 Yixun Lan
2021-05-16 12:45 Sam James
2021-05-13 21:17 Sam James
2021-05-13 18:56 Sam James
2021-05-13 17:12 Sam James
2019-11-07 8:21 Lars Wendler
2018-06-04 19:25 Mart Raudsepp
2017-12-12 15:10 Lars Wendler
2017-10-23 12:29 Manuel Rüger
2017-10-05 11:07 Sergei Trofimovich
2017-09-23 16:08 Thomas Deutschmann
2017-09-22 21:33 Thomas Deutschmann
2017-08-22 21:41 Michał Górny
2017-08-04 7:15 Lars Wendler
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=1510785750.e8e17dfd4183ebdadee86189bdf36ac78ea34e89.slyfox@gentoo \
--to=slyfox@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