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-libs/flatbuffers/
Date: Tue, 27 Jun 2023 12:36:43 +0000 (UTC)	[thread overview]
Message-ID: <1687869384.141a64ac11522afc51de98209b6b39f8c6d870c5.sam@gentoo> (raw)

commit:     141a64ac11522afc51de98209b6b39f8c6d870c5
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 27 12:36:24 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jun 27 12:36:24 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=141a64ac

dev-libs/flatbuffers: Stabilize 23.5.26 arm64, #909298

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

 dev-libs/flatbuffers/flatbuffers-23.5.26.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-libs/flatbuffers/flatbuffers-23.5.26.ebuild b/dev-libs/flatbuffers/flatbuffers-23.5.26.ebuild
index 875299414ca2..4305acae5f22 100644
--- a/dev-libs/flatbuffers/flatbuffers-23.5.26.ebuild
+++ b/dev-libs/flatbuffers/flatbuffers-23.5.26.ebuild
@@ -17,7 +17,7 @@ SRC_URI="
 
 LICENSE="Apache-2.0"
 SLOT="0/${PV}"
-KEYWORDS="amd64 ~arm ~arm64 ~riscv x86"
+KEYWORDS="amd64 ~arm arm64 ~riscv x86"
 IUSE="static-libs test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2023-06-27 12:36 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 12:36 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-12  3:03 [gentoo-commits] repo/gentoo:master commit in: dev-libs/flatbuffers/ Michał Górny
2024-04-11 19:58 Sam James
2024-04-11 17:44 Arthur Zamarin
2024-04-11 17:43 Arthur Zamarin
2024-03-26  6:57 Michał Górny
2024-03-22 12:37 Michał Górny
2024-03-22  6:14 Arthur Zamarin
2024-03-22  6:14 Arthur Zamarin
2024-03-22  4:03 Sam James
2024-03-08  5:40 Michał Górny
2024-03-07 15:39 Michał Górny
2024-02-03 19:35 Jason Zaman
2023-08-24 22:37 Sam James
2023-06-27 13:34 Michał Górny
2023-06-27 12:36 Sam James
2023-06-27 12:36 Sam James
2023-05-27  5:33 Michał Górny
2023-04-05  9:14 Michał Górny
2023-04-05  9:14 Michał Górny
2023-04-05  8:59 Jakov Smolić
2023-04-05  8:46 Jakov Smolić
2023-04-05  8:35 Arthur Zamarin
2023-03-04  4:50 Michał Górny
2023-02-03 13:34 Sam James
2023-02-03 12:47 Arthur Zamarin
2023-02-03 12:20 Sam James
2023-01-22  9:01 Michał Górny
2023-01-05  7:42 Michał Górny
2022-12-26  8:50 Andreas Sturmlechner
2022-12-07 15:59 Michał Górny
2022-12-07 14:52 Michał Górny
2022-12-07 14:52 Michał Górny
2022-08-27 11:45 Yixun Lan
2022-06-22 18:23 Sam James
2022-06-17 18:00 Sam James
2022-06-15 17:51 Andreas Sturmlechner
2022-06-02  6:08 Agostino Sarubbo
2022-06-02  6:05 Agostino Sarubbo
2022-06-02  0:15 Sam James
2022-06-01 21:26 Andreas Sturmlechner
2022-05-02  0:37 Sam James
2022-05-02  0:37 Sam James
2021-12-20 12:42 Andreas Sturmlechner
2021-12-16 21:24 Jakov Smolić
2021-12-16 21:03 Arthur Zamarin
2021-12-16 16:39 Jakov Smolić
2021-09-07 16:56 Sam James
2021-06-20 20:53 Sam James
2021-03-29 14:50 Sam James
2020-06-04 14:06 Michał Górny
2020-06-02 22:21 Mart Raudsepp
2020-04-30 20:03 Andreas Sturmlechner
2020-04-17  6:54 Agostino Sarubbo
2020-04-17  6:48 Agostino Sarubbo
2020-03-19 15:43 Andreas Sturmlechner
2019-06-28 18:21 Andreas Sturmlechner
2019-06-28 15:21 Agostino Sarubbo
2019-06-28 11:37 Agostino Sarubbo
2019-05-30 13:06 Jory Pratt
2019-05-25 11:08 Andreas Sturmlechner
2018-11-29 20:04 Mikle Kolyada
2018-11-27 21:55 Thomas Deutschmann
2018-11-05 19:15 Craig Andrews
2018-10-11 19:02 Andreas Sturmlechner
2018-10-04 19:14 Andreas Sturmlechner
2018-08-10 13:01 Michael Palimaka
2018-02-25  5:32 Michael Palimaka
2018-02-02 11:40 Michael Palimaka
2018-01-12  9:17 Michael Palimaka
2017-08-19 15:49 Andreas Sturmlechner
2017-07-29  3:42 Michael Palimaka
2017-03-04 12:30 Michael Palimaka

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=1687869384.141a64ac11522afc51de98209b6b39f8c6d870c5.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