From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/lttng-ust/
Date: Fri, 17 Mar 2023 18:35:31 +0000 (UTC) [thread overview]
Message-ID: <1679078114.5b27ccf4129c8fb11a87f78ba92f10c6cdde56aa.sam@gentoo> (raw)
commit: 5b27ccf4129c8fb11a87f78ba92f10c6cdde56aa
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 17 18:35:14 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Mar 17 18:35:14 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5b27ccf4
dev-util/lttng-ust: Stabilize 2.13.5 amd64, #901889
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/lttng-ust/lttng-ust-2.13.5.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-util/lttng-ust/lttng-ust-2.13.5.ebuild b/dev-util/lttng-ust/lttng-ust-2.13.5.ebuild
index 20dbdd7feac6..70f27a621cfa 100644
--- a/dev-util/lttng-ust/lttng-ust-2.13.5.ebuild
+++ b/dev-util/lttng-ust/lttng-ust-2.13.5.ebuild
@@ -14,7 +14,7 @@ SRC_URI="https://lttng.org/files/${PN}/${MY_P}.tar.bz2"
LICENSE="GPL-2"
SLOT="0/${MY_SLOT}"
-KEYWORDS="~alpha ~amd64 arm arm64 ~hppa ~ia64 ~loong ppc ppc64 ~riscv sparc x86"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~loong ppc ppc64 ~riscv sparc x86"
IUSE="examples numa"
DEPEND="
next reply other threads:[~2023-03-17 18:35 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 18:35 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-08 2:49 [gentoo-commits] repo/gentoo:master commit in: dev-util/lttng-ust/ Sam James
2024-11-05 15:55 Arthur Zamarin
2024-11-05 10:51 Jakov Smolić
2024-11-05 10:34 Sam James
2024-11-05 10:34 Sam James
2024-09-06 18:54 Arthur Zamarin
2024-08-27 12:04 Florian Schmaus
2024-07-19 6:05 Sam James
2024-01-23 5:53 Maciej Barć
2023-10-09 18:57 Sam James
2023-10-09 5:54 Sam James
2023-10-09 4:46 Sam James
2023-10-09 4:36 Sam James
2023-10-09 4:36 Sam James
2023-06-26 17:45 Sam James
2023-03-17 18:10 Arthur Zamarin
2023-03-17 17:58 Arthur Zamarin
2023-03-17 17:00 Sam James
2023-03-17 16:40 Arthur Zamarin
2023-03-17 16:28 Arthur Zamarin
2023-03-17 16:16 Arthur Zamarin
2022-12-27 10:23 Sam James
2022-12-04 18:45 WANG Xuerui
2022-11-05 6:27 Sam James
2022-04-26 22:10 Yixun Lan
2022-04-26 8:06 Yixun Lan
2022-04-26 8:06 Yixun Lan
2022-01-29 3:52 Sam James
2022-01-20 16:34 Sam James
2021-11-22 14:12 Jakov Smolić
2021-09-26 8:50 Yixun Lan
2021-09-19 21:53 Sam James
2021-09-19 21:53 Sam James
2021-07-25 7:56 Matt Turner
2021-03-30 15:12 Yixun Lan
2021-02-01 13:30 Sam James
2021-01-30 10:04 Sam James
2021-01-30 10:03 Sam James
2021-01-29 20:50 Sam James
2021-01-28 17:47 Sam James
2021-01-04 20:56 Andreas K. Hüttel
2021-01-04 20:14 Andreas K. Hüttel
2020-12-30 12:02 David Seifert
2020-12-29 13:38 David Seifert
2020-12-29 13:38 David Seifert
2020-12-10 2:25 Matt Turner
2020-07-19 13:37 Sergei Trofimovich
2020-04-04 9:24 Mart Raudsepp
2020-03-30 13:41 Agostino Sarubbo
2020-03-30 13:36 Agostino Sarubbo
2020-03-30 13:14 Agostino Sarubbo
2020-03-29 14:45 Sergei Trofimovich
2020-03-29 9:40 Sergei Trofimovich
2020-03-29 9:34 Sergei Trofimovich
2020-03-25 21:36 Sergei Trofimovich
2020-02-13 12:19 Agostino Sarubbo
2019-10-23 9:47 Yixun Lan
2019-10-23 9:47 Yixun Lan
2019-10-23 2:26 Yixun Lan
2019-10-22 9:58 Yixun Lan
2019-07-05 22:27 Sergei Trofimovich
2019-06-04 21:00 Agostino Sarubbo
2019-04-23 0:13 Aaron Bauman
2018-10-26 18:57 Sven Wegener
2018-10-26 14:58 Agostino Sarubbo
2018-10-26 0:52 Thomas Deutschmann
2018-10-17 14:25 Tobias Klausmann
2018-09-01 23:13 Sergei Trofimovich
2018-09-01 23:13 Sergei Trofimovich
2018-08-27 20:15 Sergei Trofimovich
2018-08-25 17:38 Michael Weber
2018-03-22 15:53 Jeroen Roovers
2017-07-11 8:41 Alexis Ballier
2016-07-01 2:44 Yixun Lan
2016-06-21 12:43 Yixun Lan
2016-02-18 7:44 Yixun Lan
2016-02-18 7:44 Yixun Lan
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=1679078114.5b27ccf4129c8fb11a87f78ba92f10c6cdde56aa.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