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: dev-util/android-tools/
Date: Wed, 22 Nov 2023 11:16:32 +0000 (UTC)	[thread overview]
Message-ID: <1700651737.0268f3ce950474e828e8fb5130b204b28789db0f.arthurzam@gentoo> (raw)

commit:     0268f3ce950474e828e8fb5130b204b28789db0f
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 22 11:15:37 2023 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Wed Nov 22 11:15:37 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0268f3ce

dev-util/android-tools: Stabilize 34.0.1 amd64, #917668

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

 dev-util/android-tools/android-tools-34.0.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-util/android-tools/android-tools-34.0.1.ebuild b/dev-util/android-tools/android-tools-34.0.1.ebuild
index 74e9b64d54ea..289192d2aae0 100644
--- a/dev-util/android-tools/android-tools-34.0.1.ebuild
+++ b/dev-util/android-tools/android-tools-34.0.1.ebuild
@@ -19,7 +19,7 @@ S="${WORKDIR}/${PN}-${MY_PV}"
 # The entire source code is Apache-2.0, except for fastboot which is BSD-2.
 LICENSE="Apache-2.0 BSD-2"
 SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~x86"
+KEYWORDS="amd64 ~arm ~arm64 ~x86"
 IUSE="python udev"
 REQUIRED_USE="python? ( ${PYTHON_REQUIRED_USE} )"
 


             reply	other threads:[~2023-11-22 11:16 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 11:16 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-22 21:50 [gentoo-commits] repo/gentoo:master commit in: dev-util/android-tools/ Zac Medico
2024-09-05  5:36 Zac Medico
2024-08-25  7:21 Zac Medico
2024-08-10 19:38 Zac Medico
2024-06-17  1:47 Sam James
2024-05-13 12:32 Arthur Zamarin
2024-05-11 15:16 Arthur Zamarin
2024-05-11 15:16 Arthur Zamarin
2024-03-25  0:23 Zac Medico
2024-03-25  0:23 Zac Medico
2024-03-02 20:09 Andreas K. Hüttel
2024-01-17  5:50 Sam James
2023-11-22 11:16 Arthur Zamarin
2023-08-22 21:27 Sam James
2023-08-22 21:25 Sam James
2023-04-19 11:07 Sam James
2023-04-19  6:49 Arthur Zamarin
2023-03-12 23:49 Zac Medico
2022-11-05 23:14 Zac Medico
2022-10-28  0:21 Zac Medico
2022-10-27  7:57 Joonas Niilola
2022-10-27  7:57 Joonas Niilola
2022-10-26 11:02 Sam James
2022-10-03  4:35 Zac Medico
2022-09-23 18:11 Zac Medico
2022-09-18  0:19 Sam James
2022-09-18  0:19 Sam James
2022-08-12 16:38 Zac Medico
2022-03-15 22:26 Mike Frysinger
2022-01-06 16:38 Zac Medico
2021-12-13 22:54 Sam James
2021-12-13 22:54 Sam James
2021-11-01  4:05 Zac Medico
2021-11-01  3:13 Zac Medico
2021-10-25  1:01 Zac Medico
2021-07-16  5:54 Zac Medico
2021-01-05 15:47 Andreas K. Hüttel
2021-01-01  0:59 Michał Górny
2020-10-13 17:05 Zac Medico
2020-10-13 17:05 Zac Medico
2020-08-12 16:22 Zac Medico
2020-07-25 19:56 Sam James
2020-07-19  0:27 Zac Medico
2020-06-30  3:51 Zac Medico
2020-05-28  6:21 Zac Medico
2020-02-10 21:00 Michał Górny
2019-12-29  9:56 David Seifert
2019-12-09  4:03 Zac Medico
2019-08-12 20:16 Michał Górny
2019-04-02  9:16 Mikle Kolyada
2018-12-31  9:11 Zac Medico
2018-12-31  5:10 Zac Medico
2018-09-28  7:44 Mikle Kolyada
2017-11-13 19:50 Manuel Rüger
2017-10-27 12:54 Thomas Deutschmann
2017-09-19 19:37 Zac Medico
2017-04-26 21:05 Zac Medico
2017-04-26 20:02 Zac Medico
2017-04-24 21:06 Zac Medico
2017-04-24  2:00 Zac Medico
2017-04-24  1:28 Zac Medico
2016-07-03  9:45 Zac Medico
2016-06-26 19:30 Zac Medico
2016-06-10 13:53 Agostino Sarubbo
2016-05-16  0:07 Zac Medico
2016-04-19  6:37 Mike Frysinger
2016-03-31  7:00 Zac Medico
2016-02-04 18:47 Mike Frysinger
2015-09-15 22:03 Zac Medico
2015-09-15 21:45 Zac Medico

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=1700651737.0268f3ce950474e828e8fb5130b204b28789db0f.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