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: gui-libs/libhandy/
Date: Mon, 15 Aug 2022 19:13:01 +0000 (UTC)	[thread overview]
Message-ID: <1660590762.11b1ef648864404cf21be29c5b7d868bf03acf2c.arthurzam@gentoo> (raw)

commit:     11b1ef648864404cf21be29c5b7d868bf03acf2c
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 15 19:12:42 2022 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Mon Aug 15 19:12:42 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=11b1ef64

gui-libs/libhandy: Stabilize 1.6.3 ppc64, #861029

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

 gui-libs/libhandy/libhandy-1.6.3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gui-libs/libhandy/libhandy-1.6.3.ebuild b/gui-libs/libhandy/libhandy-1.6.3.ebuild
index 4836879c9494..219cc2a15217 100644
--- a/gui-libs/libhandy/libhandy-1.6.3.ebuild
+++ b/gui-libs/libhandy/libhandy-1.6.3.ebuild
@@ -10,7 +10,7 @@ HOMEPAGE="https://gitlab.gnome.org/GNOME/libhandy/"
 
 LICENSE="LGPL-2.1+"
 SLOT="1"
-KEYWORDS="~alpha amd64 ~arm arm64 ~ia64 ppc ~ppc64 ~riscv ~sparc x86"
+KEYWORDS="~alpha amd64 ~arm arm64 ~ia64 ppc ppc64 ~riscv ~sparc x86"
 
 IUSE="examples glade gtk-doc +introspection test +vala"
 REQUIRED_USE="vala? ( introspection )"


             reply	other threads:[~2022-08-15 19:13 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 19:13 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-13 10:37 [gentoo-commits] repo/gentoo:master commit in: gui-libs/libhandy/ Mart Raudsepp
2024-04-07  7:40 Arthur Zamarin
2024-04-07  6:10 Arthur Zamarin
2024-02-09 22:26 Mart Raudsepp
2023-04-01 19:01 Arthur Zamarin
2023-03-30 17:44 Arthur Zamarin
2023-03-05  3:25 Matt Turner
2023-02-25 11:03 Joonas Niilola
2023-02-01 16:26 Matt Turner
2022-11-05  9:58 Arthur Zamarin
2022-10-30 23:21 Matt Turner
2022-09-16  2:40 Matt Turner
2022-09-04  3:07 Matt Turner
2022-08-15 19:13 Arthur Zamarin
2022-07-29  2:59 Sam James
2022-07-09 23:39 Matt Turner
2022-05-28  5:05 Sam James
2022-04-23  5:00 Matt Turner
2022-03-20 19:54 Matt Turner
2022-01-24 14:49 Sam James
2022-01-24  3:39 Sam James
2022-01-20 10:02 Jakov Smolić
2022-01-20  9:42 Arthur Zamarin
2021-12-18  3:47 Matt Turner
2021-09-15 20:00 Mart Raudsepp
2021-07-26  7:15 Matt Turner
2021-07-24 17:08 Sam James
2021-07-11 20:48 Sam James
2021-06-21 23:59 Matt Turner
2021-05-29 15:27 Sam James
2021-05-28 19:20 Sam James
2021-04-27 22:17 Matt Turner
2021-04-14 20:45 Matt Turner
2021-04-12 23:11 Sam James
2021-02-26 19:02 Sam James
2021-01-08  4:15 Matt Turner
2020-12-19 11:04 Mart Raudsepp
2020-12-19 11:04 Mart Raudsepp
2020-12-11  3:24 Matt Turner
2020-04-25 20:17 Mart Raudsepp
2020-03-14 21:08 Mart Raudsepp
2020-01-31 20:10 Mart Raudsepp
2019-11-30 21:17 Sergei Trofimovich
2019-09-28 11:27 Sergei Trofimovich
2019-09-07 23:18 Thomas Deutschmann
2019-09-07 22:09 Mart Raudsepp
2019-08-25  1:10 Aaron Bauman
2019-08-17 17:50 Mart Raudsepp

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=1660590762.11b1ef648864404cf21be29c5b7d868bf03acf2c.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