public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libtraceevent/
Date: Sun,  4 Feb 2024 21:42:23 +0000 (UTC)	[thread overview]
Message-ID: <1707082911.1841c29fcdfd4f0386a08733a59808cbe03e7b8e.ionen@gentoo> (raw)

commit:     1841c29fcdfd4f0386a08733a59808cbe03e7b8e
Author:     Matoro Mahri <matoro_gentoo <AT> matoro <DOT> tk>
AuthorDate: Sat Feb  3 17:37:58 2024 +0000
Commit:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Sun Feb  4 21:41:51 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1841c29f

dev-libs/libtraceevent: Keyword 1.7.3 alpha, #922878

Signed-off-by: Matoro Mahri <matoro_gentoo <AT> matoro.tk>
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>

 dev-libs/libtraceevent/libtraceevent-1.7.3.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-libs/libtraceevent/libtraceevent-1.7.3.ebuild b/dev-libs/libtraceevent/libtraceevent-1.7.3.ebuild
index a7e867c7ad0e..3c3393a863c3 100644
--- a/dev-libs/libtraceevent/libtraceevent-1.7.3.ebuild
+++ b/dev-libs/libtraceevent/libtraceevent-1.7.3.ebuild
@@ -1,4 +1,4 @@
-# Copyright 2019-2023 Gentoo Authors
+# Copyright 2019-2024 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -13,7 +13,7 @@ if [[ ${PV} =~ [9]{4,} ]]; then
 	inherit git-r3
 else
 	SRC_URI="https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/snapshot/${P}.tar.gz"
-	KEYWORDS="~amd64 ~arm ~arm64 ~loong ~ppc ~ppc64 ~riscv ~x86"
+	KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~loong ~ppc ~ppc64 ~riscv ~x86"
 fi
 
 LICENSE="LGPL-2.1"


             reply	other threads:[~2024-02-04 21:42 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-04 21:42 Ionen Wolkens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-26  7:18 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libtraceevent/ Arthur Zamarin
2025-04-26  3:40 Sam James
2025-04-26  2:56 Sam James
2025-04-26  1:45 Sam James
2025-04-26  1:25 Sam James
2024-11-01  3:12 Yixun Lan
2024-11-01  3:12 Yixun Lan
2024-10-27  6:50 Arthur Zamarin
2024-10-25 22:53 Sam James
2024-10-25 22:09 Sam James
2024-10-25 22:09 Sam James
2024-10-25 22:09 Sam James
2024-08-26  0:03 Yixun Lan
2024-08-23 12:35 Yixun Lan
2024-05-30  7:53 Yixun Lan
2024-05-30  1:51 Yixun Lan
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
2023-07-11 11:03 WANG Xuerui
2023-06-11 20:22 Arthur Zamarin
2023-06-11 19:20 Arthur Zamarin
2023-06-11 19:16 Arthur Zamarin
2023-06-10  9:12 Sam James
2023-06-10  9:12 Sam James
2023-06-10  9:12 Sam James
2023-05-17 12:32 Yixun Lan
2023-05-17 12:32 Yixun Lan
2023-03-22  5:27 Sam James
2023-01-19 22:51 Yixun Lan
2023-01-12 23:35 Yixun Lan
2023-01-11  8:03 Arthur Zamarin
2022-12-22  6:12 Yixun Lan
2022-12-20  1:56 Yixun Lan
2022-10-08  1:54 Yixun Lan
2022-09-02 13:59 Yixun Lan
2022-09-02 13:59 Yixun Lan
2022-07-29 12:12 Arthur Zamarin
2022-06-16 22:54 Patrick McLean
2022-06-16 16:58 Patrick McLean

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=1707082911.1841c29fcdfd4f0386a08733a59808cbe03e7b8e.ionen@gentoo \
    --to=ionen@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