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-libs/libsigc++/
Date: Sun,  7 Apr 2024 08:38:57 +0000 (UTC)	[thread overview]
Message-ID: <1712479129.382d4bccb865415ca8e3144082d608e5dc66ffae.arthurzam@gentoo> (raw)

commit:     382d4bccb865415ca8e3144082d608e5dc66ffae
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sun Apr  7 08:38:49 2024 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sun Apr  7 08:38:49 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=382d4bcc

dev-libs/libsigc++: Stabilize 3.6.0 ppc64, #928817

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

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

diff --git a/dev-libs/libsigc++/libsigc++-3.6.0.ebuild b/dev-libs/libsigc++/libsigc++-3.6.0.ebuild
index a7f3cdd14400..420f8bccda21 100644
--- a/dev-libs/libsigc++/libsigc++-3.6.0.ebuild
+++ b/dev-libs/libsigc++/libsigc++-3.6.0.ebuild
@@ -10,7 +10,7 @@ HOMEPAGE="https://libsigcplusplus.github.io/libsigcplusplus/
 
 LICENSE="LGPL-2.1+"
 SLOT="3"
-KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~loong ~mips ~ppc ~ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
+KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~loong ~mips ~ppc ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
 IUSE="gtk-doc test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2024-04-07  8:39 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-07  8:38 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: dev-libs/libsigc++/ Mart Raudsepp
2024-04-09 22:46 Sam James
2024-04-07  9:14 Arthur Zamarin
2024-04-07  6:21 Arthur Zamarin
2023-10-08 10:30 Pacho Ramos
2023-02-17  8:23 Arthur Zamarin
2023-02-17  8:23 Arthur Zamarin
2023-02-16 18:39 Arthur Zamarin
2023-02-16 18:39 Arthur Zamarin
2023-02-16 18:39 Arthur Zamarin
2023-02-16 18:39 Arthur Zamarin
2022-12-24  2:16 Matt Turner
2022-12-24  2:11 Matt Turner
2022-11-12  6:01 WANG Xuerui
2022-10-30  1:50 Matt Turner
2022-09-24  3:43 Matt Turner
2022-09-24  3:43 Matt Turner
2022-05-19  5:08 WANG Xuerui
2022-04-18 20:48 Jakov Smolić
2022-03-15 20:54 Matt Turner
2022-03-09 15:39 Sam James
2022-03-09 12:49 Sam James
2022-03-08 12:32 Sam James
2022-02-12  3:48 Matt Turner
2022-01-02 10:54 Jakov Smolić
2021-08-12  3:10 Yixun Lan
2021-05-28 19:18 Sam James
2021-05-22  2:27 Matt Turner
2021-05-22  2:27 Matt Turner
2021-04-13 15:00 Sam James
2021-04-12 23:11 Sam James
2021-04-12 16:02 Sam James
2021-03-30 17:49 Andreas Sturmlechner
2021-03-15 18:06 Sergei Trofimovich
2021-01-18 21:10 Matt Turner
2020-09-21 21:31 Conrad Kostecki
2020-09-18  7:44 Sergei Trofimovich
2020-09-18  6:48 Sergei Trofimovich
2020-06-28 20:30 Agostino Sarubbo
2020-06-25 18:14 Sergei Trofimovich
2020-04-04 12:07 Mart Raudsepp
2019-02-28 15:35 Mikle Kolyada
2019-02-26 21:19 Sergei Trofimovich
2019-02-17 21:05 Mikle Kolyada
2019-02-17 17:14 Sergei Trofimovich
2019-02-17 17:08 Sergei Trofimovich
2019-02-17 16:57 Sergei Trofimovich
2019-02-16  6:08 Mikle Kolyada
2019-02-15 15:46 Thomas Deutschmann
2019-02-14 22:09 Sergei Trofimovich
2018-10-31 13:17 Mart Raudsepp
2017-07-07 21:20 Mart Raudsepp
2017-07-07 10:12 Agostino Sarubbo
2017-06-12 10:07 Mart Raudsepp
2017-04-22 17:53 Tobias Klausmann
2017-03-29  7:45 Michael Weber
2017-03-28 15:09 Michael Weber
2017-03-28 14:59 Michael Weber
2016-12-06 20:05 Markus Meier
2016-11-01 23:58 Gilles Dartiguelongue
2016-05-03 19:27 Markus Meier
2016-03-16 14:09 Agostino Sarubbo
2015-11-14 13:48 Pacho Ramos
2015-11-14 13:48 Pacho Ramos

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=1712479129.382d4bccb865415ca8e3144082d608e5dc66ffae.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