public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: java-virtuals/servlet-api/
Date: Sun, 20 Feb 2022 19:34:46 +0000 (UTC)	[thread overview]
Message-ID: <1645385673.89ae5e18cfe8cc824d1c8fc3def0116198558e9b.arthurzam@gentoo> (raw)

commit:     89ae5e18cfe8cc824d1c8fc3def0116198558e9b
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 20 19:34:33 2022 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sun Feb 20 19:34:33 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=89ae5e18

java-virtuals/servlet-api: Stabilize 3.1-r1 arm64, #833790

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 java-virtuals/servlet-api/servlet-api-3.1-r1.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/java-virtuals/servlet-api/servlet-api-3.1-r1.ebuild b/java-virtuals/servlet-api/servlet-api-3.1-r1.ebuild
index 0d0e35836931..73a2c05b650e 100644
--- a/java-virtuals/servlet-api/servlet-api-3.1-r1.ebuild
+++ b/java-virtuals/servlet-api/servlet-api-3.1-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2020 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -11,7 +11,7 @@ SRC_URI=""
 
 LICENSE="public-domain"
 SLOT="${PV}"
-KEYWORDS="amd64 ~arm ~arm64 ppc64 x86"
+KEYWORDS="amd64 ~arm arm64 ppc64 x86"
 
 RDEPEND="|| (
 		dev-java/tomcat-servlet-api:${SLOT}


             reply	other threads:[~2022-02-20 19:35 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-20 19:34 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-05  9:53 [gentoo-commits] repo/gentoo:master commit in: java-virtuals/servlet-api/ Miroslav Šulc
2023-02-05  9:53 Miroslav Šulc
2022-09-19 12:12 Florian Schmaus
2022-06-09  6:45 Sam James
2022-06-08  9:58 Jakov Smolić
2022-06-08  9:58 Jakov Smolić
2022-06-08  8:46 Agostino Sarubbo
2022-06-08  8:42 Agostino Sarubbo
2022-06-08  7:57 Jakov Smolić
2022-06-08  7:57 Jakov Smolić
2022-05-09 19:13 Florian Schmaus
2022-02-20 19:34 Arthur Zamarin
2022-02-09  1:25 Sam James
2022-02-09  1:25 Sam James
2022-01-29  8:32 Miroslav Šulc
2022-01-28 20:12 Arthur Zamarin
2022-01-28 20:12 Arthur Zamarin
2022-01-28 13:06 Jakov Smolić
2022-01-28 13:06 Jakov Smolić
2022-01-28 11:28 Jakov Smolić
2022-01-28 11:28 Jakov Smolić
2022-01-07 20:42 Arthur Zamarin
2022-01-07 20:42 Arthur Zamarin
2022-01-07 20:40 Arthur Zamarin
2022-01-07  8:18 Miroslav Šulc
2021-12-29  8:50 Miroslav Šulc
2021-05-16 18:58 Sam James
2021-01-06 13:48 Fabian Groffen
2020-07-25  2:51 Sam James
2019-10-16  8:10 Miroslav Šulc
2018-03-01 15:09 Michał Górny
2018-02-02  9:05 Fabian Groffen
2018-02-02  9:05 Fabian Groffen
2017-08-28 22:01 James Le Cuirot
2017-08-28 22:01 James Le Cuirot
2017-07-14 21:35 Alexis Ballier
2017-07-13 18:32 Alexis Ballier
2017-06-24 21:49 Patrice Clement
2017-06-24 21:49 Patrice Clement
2017-06-24 21:49 Patrice Clement
2017-02-24  0:34 Michael Weber
2015-09-26  8:14 Patrice Clement

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=1645385673.89ae5e18cfe8cc824d1c8fc3def0116198558e9b.arthurzam@gentoo \
    --to=arthurzam@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