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-util/xfce4-dev-tools/
Date: Thu,  2 Nov 2023 04:12:31 +0000 (UTC)	[thread overview]
Message-ID: <1698898256.d00c88a37f9f3f8f6df82ba2d4191b1d9eaea69e.sam@gentoo> (raw)

commit:     d00c88a37f9f3f8f6df82ba2d4191b1d9eaea69e
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Nov  2 04:06:24 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Nov  2 04:10:56 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d00c88a3

dev-util/xfce4-dev-tools: Stabilize 4.18.1 arm, #916665

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

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

diff --git a/dev-util/xfce4-dev-tools/xfce4-dev-tools-4.18.1.ebuild b/dev-util/xfce4-dev-tools/xfce4-dev-tools-4.18.1.ebuild
index f852684c9f8f..f22bdb1f127b 100644
--- a/dev-util/xfce4-dev-tools/xfce4-dev-tools-4.18.1.ebuild
+++ b/dev-util/xfce4-dev-tools/xfce4-dev-tools-4.18.1.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://archive.xfce.org/src/xfce/${PN}/${PV%.*}/${P}.tar.bz2"
 
 LICENSE="GPL-2+"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~mips ppc ~ppc64 ~riscv ~sparc x86 ~amd64-linux ~x86-linux ~x64-solaris"
+KEYWORDS="~alpha ~amd64 arm ~arm64 ~hppa ~ia64 ~loong ~mips ppc ~ppc64 ~riscv ~sparc x86 ~amd64-linux ~x86-linux ~x64-solaris"
 
 DEPEND="
 	>=dev-libs/glib-2.66.0


             reply	other threads:[~2023-11-02  4:12 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  4:12 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-02 13:03 [gentoo-commits] repo/gentoo:master commit in: dev-util/xfce4-dev-tools/ Michał Górny
2023-11-02 12:58 Michał Górny
2023-11-02  4:12 Sam James
2023-11-02  4:12 Sam James
2023-11-02  4:12 Sam James
2023-11-01 20:37 Arthur Zamarin
2023-11-01 20:37 Arthur Zamarin
2023-10-18  7:31 Michał Górny
2023-03-17 10:50 Michał Górny
2023-03-17  8:56 Arthur Zamarin
2023-03-15  6:55 Michał Górny
2023-03-05 11:05 Michał Górny
2023-02-03 16:53 Sam James
2023-02-03 14:21 Arthur Zamarin
2023-02-03 14:21 Arthur Zamarin
2023-02-03 13:32 Arthur Zamarin
2022-12-15 15:04 Michał Górny
2022-12-15 15:04 Michał Górny
2022-12-01 13:55 Michał Górny
2022-10-29 15:31 Michał Górny
2022-07-02 23:23 WANG Xuerui
2021-10-09  7:52 Michał Górny
2021-07-25 18:04 Michał Górny
2021-05-25 14:21 Yixun Lan
2021-02-15  8:38 Sam James
2020-12-22 23:35 Michał Górny
2020-12-16 13:29 Michał Górny
2020-12-02 10:23 Sam James
2020-11-02 21:00 Michał Górny
2020-06-25 14:34 Michał Górny
2019-10-13 11:24 Mikle Kolyada
2019-10-12 21:00 Sergei Trofimovich
2019-08-11 17:45 Michał Górny
2019-06-28  9:08 Michał Górny
2018-03-03 17:48 Tobias Klausmann
2018-01-10 21:22 Sergei Trofimovich
2018-01-08  8:00 Sergei Trofimovich
2018-01-07 20:32 Sergei Trofimovich
2018-01-07 13:17 Sergei Trofimovich
2018-01-06  5:05 Thomas Deutschmann
2018-01-05 10:27 Mikle Kolyada
2017-11-27 21:25 Denis Dupeyron
2015-10-17 18:32 Mikle Kolyada

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=1698898256.d00c88a37f9f3f8f6df82ba2d4191b1d9eaea69e.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