From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/yajl/
Date: Sat, 15 Jul 2023 07:12:27 +0000 (UTC) [thread overview]
Message-ID: <1689405137.6fbb5b32b821d6b14c4cd08917ae43aeef3302db.sam@gentoo> (raw)
commit: 6fbb5b32b821d6b14c4cd08917ae43aeef3302db
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 15 07:12:17 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Jul 15 07:12:17 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6fbb5b32
dev-libs/yajl: Stabilize 2.1.0-r4 ppc64, #910383
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-libs/yajl/yajl-2.1.0-r4.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/yajl/yajl-2.1.0-r4.ebuild b/dev-libs/yajl/yajl-2.1.0-r4.ebuild
index e3bfdf308697..c41296994daa 100644
--- a/dev-libs/yajl/yajl-2.1.0-r4.ebuild
+++ b/dev-libs/yajl/yajl-2.1.0-r4.ebuild
@@ -12,7 +12,7 @@ S="${WORKDIR}/lloyd-yajl-66cb08c"
LICENSE="ISC"
SLOT="0/2"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~ppc ~ppc64 ~riscv ~s390 sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~ppc ppc64 ~riscv ~s390 sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
IUSE=""
PATCHES=(
next reply other threads:[~2023-07-15 7:12 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 7:12 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-23 17:20 [gentoo-commits] repo/gentoo:master commit in: dev-libs/yajl/ Hans de Graaff
2024-10-15 12:47 Arthur Zamarin
2024-10-09 6:59 Arthur Zamarin
2024-10-09 5:46 Sam James
2024-10-06 14:29 Arthur Zamarin
2024-10-06 12:01 Sam James
2024-10-06 11:21 Sam James
2023-12-28 8:21 Hans de Graaff
2023-08-17 20:03 Hans de Graaff
2023-08-02 9:05 Arthur Zamarin
2023-07-15 13:51 Arthur Zamarin
2023-07-15 9:22 Arthur Zamarin
2023-07-15 8:19 Arthur Zamarin
2023-07-15 8:19 Arthur Zamarin
2023-07-15 7:09 Sam James
2022-11-16 5:57 WANG Xuerui
2022-10-15 14:00 Sam James
2022-04-26 2:46 Sam James
2021-07-28 15:30 Marek Szuba
2021-03-07 9:38 Andreas Sturmlechner
2021-03-07 9:38 Andreas Sturmlechner
2021-01-06 19:34 Fabian Groffen
2019-07-28 14:09 Mikle Kolyada
2019-05-26 7:04 Sergei Trofimovich
2019-05-24 22:50 Sergei Trofimovich
2019-05-22 7:36 Sergei Trofimovich
2019-05-21 22:43 Aaron Bauman
2019-05-19 20:43 Mikle Kolyada
2019-05-19 13:14 Thomas Deutschmann
2019-05-14 8:08 Sergei Trofimovich
2019-04-27 15:20 Sergei Trofimovich
2018-10-04 9:06 Andreas Sturmlechner
2018-10-04 8:36 Mikle Kolyada
2018-09-14 8:28 Tobias Klausmann
2018-08-25 18:55 Sergei Trofimovich
2018-08-25 18:25 Sergei Trofimovich
2018-08-25 18:11 Sergei Trofimovich
2018-08-23 8:34 Sergei Trofimovich
2018-08-23 2:34 Mikle Kolyada
2018-08-23 1:41 Thomas Deutschmann
2017-10-16 0:08 David Seifert
2017-01-21 12:00 Jeroen Roovers
2017-01-20 11:05 Agostino Sarubbo
2017-01-17 14:24 Agostino Sarubbo
2017-01-11 10:35 Agostino Sarubbo
2016-12-20 18:13 Thomas Deutschmann
2016-12-20 17:31 Tobias Klausmann
2016-11-15 14:53 Tobias Klausmann
2016-11-13 8:55 Markus Meier
2016-03-27 14:18 Doug Goldstein
2016-03-21 21:49 Doug Goldstein
2016-03-21 21:49 Doug Goldstein
2016-03-21 21:49 Doug Goldstein
2016-03-21 21:49 Doug Goldstein
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=1689405137.6fbb5b32b821d6b14c4cd08917ae43aeef3302db.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