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-java/antlr/
Date: Thu, 17 Mar 2022 01:36:52 +0000 (UTC)	[thread overview]
Message-ID: <1647480998.5020446e751cbaad2da0847e6c551355bd6aaa73.sam@gentoo> (raw)

commit:     5020446e751cbaad2da0847e6c551355bd6aaa73
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 17 01:36:38 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Mar 17 01:36:38 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5020446e

dev-java/antlr: Stabilize 4.9.3 ppc64, #834702

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

 dev-java/antlr/antlr-4.9.3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-java/antlr/antlr-4.9.3.ebuild b/dev-java/antlr/antlr-4.9.3.ebuild
index 0a6fdef4c5ec..be89da27f17e 100644
--- a/dev-java/antlr/antlr-4.9.3.ebuild
+++ b/dev-java/antlr/antlr-4.9.3.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://github.com/${PN}/${PN}4/archive/${PV}.tar.gz -> ${P}.tar.gz"
 
 LICENSE="BSD"
 SLOT="4"
-KEYWORDS="amd64 ~arm arm64 ~ppc64 x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="amd64 ~arm arm64 ppc64 x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
 
 CP_DEPEND="
 	~dev-java/antlr-runtime-${PV}:${SLOT}


             reply	other threads:[~2022-03-17  1:36 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17  1:36 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-15  7:45 [gentoo-commits] repo/gentoo:master commit in: dev-java/antlr/ Miroslav Šulc
2022-05-13 17:09 Miroslav Šulc
2022-05-13 14:15 Jakov Smolić
2022-05-12  8:24 Jakov Smolić
2022-05-12  8:24 Jakov Smolić
2022-05-11 14:50 Agostino Sarubbo
2022-04-11  6:19 Miroslav Šulc
2022-03-17  8:56 Miroslav Šulc
2022-03-17  2:09 Sam James
2022-03-17  0:57 Sam James
2022-03-17  0:21 Sam James
2022-03-09  9:19 Agostino Sarubbo
2022-03-08 13:04 Agostino Sarubbo
2022-02-25 21:31 Sam James
2022-02-24  8:46 Jakov Smolić
2022-02-24  8:46 Jakov Smolić
2022-02-04  8:17 Miroslav Šulc
2022-01-25  9:30 Miroslav Šulc
2021-11-23 21:36 Sam James
2021-11-23 21:36 Sam James
2021-07-18  6:33 Agostino Sarubbo
2021-06-19 11:54 Miroslav Šulc
2021-06-19 10:01 Agostino Sarubbo
2021-06-19  7:53 Miroslav Šulc
2021-06-19  7:53 Miroslav Šulc
2021-06-18 22:28 Sam James
2021-06-18 15:46 Sam James
2021-05-27  8:04 Miroslav Šulc
2021-05-16 19:06 Miroslav Šulc
2021-05-16 19:06 Miroslav Šulc
2021-05-16 19:06 Miroslav Šulc
2021-04-28  9:23 Miroslav Šulc
2020-12-14 11:27 Miroslav Šulc
2020-07-25  2:21 Sam James
2020-07-20  1:10 Sam James
2019-04-20  1:29 Aaron Bauman
2018-03-01  8:39 Michał Górny
2017-07-13 12:13 Alexis Ballier
2017-03-20 11:06 Patrice Clement
2017-01-29 15:41 Fabian Groffen
2016-10-07 20:55 James Le Cuirot
2016-10-07 20:55 James Le Cuirot
2016-10-07 20:55 James Le Cuirot
2016-01-14 21:44 James Le Cuirot
2016-01-14 21:44 James Le Cuirot
2015-12-06 13:46 James Le Cuirot
2015-10-14 15:22 James Le Cuirot
2015-10-14 15:22 James Le Cuirot

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=1647480998.5020446e751cbaad2da0847e6c551355bd6aaa73.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