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-libs/libgee/
Date: Wed,  9 Mar 2022 15:39:17 +0000 (UTC)	[thread overview]
Message-ID: <1646840283.83803dcbae0aa4f0cdb57d525028717d87b38161.sam@gentoo> (raw)

commit:     83803dcbae0aa4f0cdb57d525028717d87b38161
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Mar  9 15:38:03 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Mar  9 15:38:03 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=83803dcb

dev-libs/libgee: Stabilize 0.20.5 ppc64, #834426

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

 dev-libs/libgee/libgee-0.20.5.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-libs/libgee/libgee-0.20.5.ebuild b/dev-libs/libgee/libgee-0.20.5.ebuild
index f64a42d8f965..4acf9674839f 100644
--- a/dev-libs/libgee/libgee-0.20.5.ebuild
+++ b/dev-libs/libgee/libgee-0.20.5.ebuild
@@ -10,7 +10,7 @@ HOMEPAGE="https://wiki.gnome.org/Projects/Libgee"
 
 LICENSE="LGPL-2.1+"
 SLOT="0.8/2"
-KEYWORDS="~alpha amd64 arm arm64 ~ia64 ppc ~ppc64 ~riscv ~sparc x86 ~x86-linux"
+KEYWORDS="~alpha amd64 arm arm64 ~ia64 ppc ppc64 ~riscv ~sparc x86 ~x86-linux"
 IUSE="+introspection"
 
 # FIXME: add doc support, requires valadoc


             reply	other threads:[~2022-03-09 15:39 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 15:39 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-02 22:33 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libgee/ Mart Raudsepp
2023-12-29 17:14 Arthur Zamarin
2023-12-27 12:27 Arthur Zamarin
2023-12-27 12:27 Arthur Zamarin
2023-12-27 12:27 Arthur Zamarin
2023-12-27 12:27 Arthur Zamarin
2023-12-27 12:27 Arthur Zamarin
2023-12-27 12:27 Arthur Zamarin
2023-12-14  4:12 Sam James
2023-10-01 12:02 Sam James
2023-10-01 12:02 Sam James
2023-10-01  7:55 Sam James
2023-10-01  7:55 Sam James
2023-07-27  5:46 WANG Xuerui
2022-11-05 18:58 Arthur Zamarin
2022-11-05  9:58 Arthur Zamarin
2022-11-05  9:44 Arthur Zamarin
2022-10-30  1:50 Matt Turner
2022-09-24 20:05 Matt Turner
2022-03-15 20:54 Matt Turner
2022-03-09 12:49 Sam James
2022-03-08 12:32 Sam James
2022-02-11 20:56 Matt Turner
2021-05-28 19:18 Sam James
2021-04-12 21:59 Matt Turner
2020-12-31  1:47 Sam James
2020-12-06  5:13 Matt Turner
2020-06-07 21:28 Mart Raudsepp
2020-05-13 17:35 Sergei Trofimovich
2020-04-22 14:25 Agostino Sarubbo
2020-04-22  8:44 Agostino Sarubbo
2020-04-22  8:41 Agostino Sarubbo
2020-02-12 15:52 Mart Raudsepp
2020-01-11 20:19 Mart Raudsepp
2020-01-11 20:19 Mart Raudsepp
2019-10-13 19:04 Matt Turner
2019-09-14 23:36 Sergei Trofimovich
2019-09-08  1:13 Thomas Deutschmann
2019-09-02 10:11 Agostino Sarubbo
2019-09-02  9:32 Agostino Sarubbo
2019-09-01 18:20 Mikle Kolyada
2019-08-31  5:26 Mikle Kolyada
2019-08-05 18:58 Pacho Ramos
2018-12-06 18:18 Mart Raudsepp
2018-07-25 22:08 Mart Raudsepp
2018-05-29 12:29 Mikle Kolyada
2018-05-14 14:11 Tobias Klausmann
2018-05-04 20:46 Markus Meier
2018-04-28 17:05 Sergei Trofimovich
2018-04-28 16:36 Sergei Trofimovich
2018-04-26 17:15 Thomas Deutschmann
2018-04-23 19:30 Mart Raudsepp
2017-12-27 13:02 Mart Raudsepp
2017-12-27  8:35 Markus Meier
2017-12-02 10:41 Sergei Trofimovich
2017-11-18 13:20 Sergei Trofimovich
2017-11-06 20:49 Tobias Klausmann
2017-11-04 13:04 Sergei Trofimovich
2017-08-17  7:40 Gilles Dartiguelongue
2017-06-30  6:02 Alexis Ballier
2017-02-24 23:04 Mart Raudsepp
2017-02-24 21:29 Michael Weber
2017-02-21  9:16 Tobias Klausmann
2017-02-15 19:24 Mart Raudsepp
2016-10-15 15:42 Gilles Dartiguelongue
2016-10-15 15:42 Gilles Dartiguelongue
2016-09-02 16:58 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=1646840283.83803dcbae0aa4f0cdb57d525028717d87b38161.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