public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/pahole/
Date: Sun, 16 Jul 2023 14:23:49 +0000 (UTC)	[thread overview]
Message-ID: <1689517418.a68b1fd388c81be3e938be029c7fbbd2a43609ab.sam@gentoo> (raw)

commit:     a68b1fd388c81be3e938be029c7fbbd2a43609ab
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Jul 16 14:23:38 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Jul 16 14:23:38 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a68b1fd3

dev-util/pahole: Stabilize 1.25 arm, #910429

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-util/pahole/pahole-1.25.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-util/pahole/pahole-1.25.ebuild b/dev-util/pahole/pahole-1.25.ebuild
index 04f2fb615103..a37c20430dbe 100644
--- a/dev-util/pahole/pahole-1.25.ebuild
+++ b/dev-util/pahole/pahole-1.25.ebuild
@@ -37,7 +37,7 @@ LICENSE="GPL-2" # only
 SLOT="0"
 IUSE="debug"
 if [[ ${PV} != 9999 ]] ; then
-	KEYWORDS="amd64 ~arm ~arm64 ~loong ~ppc ppc64 ~riscv ~x86"
+	KEYWORDS="amd64 arm ~arm64 ~loong ~ppc ppc64 ~riscv ~x86"
 fi
 REQUIRED_USE="${PYTHON_REQUIRED_USE}"
 


             reply	other threads:[~2023-07-16 14:23 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-16 14:23 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-04  7:58 [gentoo-commits] repo/gentoo:master commit in: dev-util/pahole/ Sam James
2024-09-05 17:59 Sam James
2024-09-05 14:32 Sam James
2024-09-05 14:30 Sam James
2024-09-05 14:30 Sam James
2024-09-05 12:35 Sam James
2024-09-05 12:33 Sam James
2024-09-05 12:33 Sam James
2024-08-25 10:18 Jakov Smolić
2024-08-25 10:18 Jakov Smolić
2024-08-25 10:18 Jakov Smolić
2024-08-25 10:18 Jakov Smolić
2024-08-25  9:51 Arthur Zamarin
2024-08-25  9:51 Arthur Zamarin
2024-06-24 13:06 Matthias Schwarzott
2024-06-22  5:50 Matthias Schwarzott
2024-06-20 10:31 Sam James
2024-06-05  6:32 Matthias Schwarzott
2024-05-28 13:54 Matthias Schwarzott
2024-03-13  4:48 Sam James
2024-03-10 23:21 Jakov Smolić
2024-03-10 20:00 Arthur Zamarin
2024-03-10 20:00 Arthur Zamarin
2024-03-10 19:52 Arthur Zamarin
2024-03-10 19:52 Arthur Zamarin
2024-02-28 20:10 Matthias Schwarzott
2023-07-16 14:23 Sam James
2023-07-16 14:23 Sam James
2023-07-16 14:23 Sam James
2023-07-16 14:20 Sam James
2023-07-11 11:03 WANG Xuerui
2023-06-30  4:37 Matthias Schwarzott
2023-04-15  7:17 Matthias Schwarzott
2023-03-22 18:45 Andreas Sturmlechner
2023-03-13 22:11 Sam James
2023-03-13 21:24 Sam James
2023-03-13 20:51 Sam James
2023-03-13 20:51 Sam James
2023-03-13 20:35 Arthur Zamarin
2023-01-19  2:49 Sam James
2022-09-05  7:35 Matthias Schwarzott
2022-06-05  2:32 Matt Turner
2022-05-22  0:54 Yixun Lan
2022-05-20  6:11 Matthias Schwarzott
2022-05-20  6:11 Matthias Schwarzott
2022-04-15  6:36 Arthur Zamarin
2022-04-13 23:01 Sam James
2022-03-12 16:26 Arthur Zamarin
2022-03-10 10:10 Jakov Smolić
2022-03-10  9:03 Jakov Smolić
2021-12-17 11:45 Matthias Schwarzott
2021-12-16 21:45 Georgy Yakovlev
2021-11-07 16:16 罗百科
2021-06-02  8:20 Matthias Schwarzott

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=1689517418.a68b1fd388c81be3e938be029c7fbbd2a43609ab.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