From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-cpp/glog/
Date: Sat, 18 Nov 2017 10:03:01 +0000 (UTC) [thread overview]
Message-ID: <1510999232.5fc39f340611550bdc06c27983d6f60d7aba3ae0.slyfox@gentoo> (raw)
commit: 5fc39f340611550bdc06c27983d6f60d7aba3ae0
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 18 10:00:32 2017 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Nov 18 10:00:32 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5fc39f34
dev-cpp/glog: stable 0.3.4-r1 for ppc64, bug #636226
Package-Manager: Portage-2.3.14, Repoman-2.3.6
RepoMan-Options: --include-arches="ppc64"
dev-cpp/glog/glog-0.3.4-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-cpp/glog/glog-0.3.4-r1.ebuild b/dev-cpp/glog/glog-0.3.4-r1.ebuild
index 02b13e3cecf..100a82d8f0d 100644
--- a/dev-cpp/glog/glog-0.3.4-r1.ebuild
+++ b/dev-cpp/glog/glog-0.3.4-r1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/google/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="BSD"
SLOT="0"
-KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-linux ~x86-linux"
IUSE="gflags static-libs test unwind"
RDEPEND="
next reply other threads:[~2017-11-18 10:03 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 10:03 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-18 21:31 [gentoo-commits] repo/gentoo:master commit in: dev-cpp/glog/ Sam James
2025-07-14 13:41 Arthur Zamarin
2025-07-14 13:41 Arthur Zamarin
2025-07-14 13:41 Arthur Zamarin
2025-07-14 13:41 Arthur Zamarin
2025-07-14 13:41 Arthur Zamarin
2025-05-25 22:53 Sam James
2025-03-18 0:57 Sam James
2025-03-18 0:55 Sam James
2025-03-02 10:48 Sam James
2024-12-01 2:34 Sam James
2023-12-24 10:57 WANG Xuerui
2022-08-03 17:30 Arthur Zamarin
2022-08-03 7:49 Agostino Sarubbo
2022-08-03 4:45 Arthur Zamarin
2022-07-07 13:59 Yixun Lan
2022-05-16 12:51 Agostino Sarubbo
2022-04-26 21:49 Sam James
2022-04-26 16:56 Arthur Zamarin
2022-04-26 14:01 Arthur Zamarin
2022-04-26 14:01 Arthur Zamarin
2022-04-26 6:56 Agostino Sarubbo
2022-04-26 3:48 Sam James
2022-04-26 3:48 Sam James
2022-04-26 2:53 Sam James
2022-04-06 6:24 Jakov Smolić
2022-02-03 3:46 Sam James
2022-01-29 15:20 Yixun Lan
2022-01-29 15:20 Yixun Lan
2021-04-02 15:00 Mike Gilbert
2020-07-12 9:26 Sergei Trofimovich
2020-07-12 9:26 Sergei Trofimovich
2020-04-23 7:16 Sergei Trofimovich
2020-04-04 11:07 Sergei Trofimovich
2020-01-17 19:09 Mike Gilbert
2020-01-01 19:43 Agostino Sarubbo
2019-12-31 18:08 Aaron Bauman
2019-12-31 8:18 Agostino Sarubbo
2019-12-31 8:15 Agostino Sarubbo
2019-12-29 19:34 Mike Gilbert
2019-12-29 19:34 Mike Gilbert
2019-12-29 19:34 Mike Gilbert
2019-08-11 17:20 Thomas Deutschmann
2019-08-11 17:20 Thomas Deutschmann
2019-08-11 15:57 Thomas Deutschmann
2018-04-26 15:14 Mike Gilbert
2018-01-04 9:08 Mike Frysinger
2017-11-18 10:13 Sergei Trofimovich
2017-10-11 18:15 Manuel Rüger
2017-02-22 22:54 Michael Weber
2016-03-02 18:18 Mike Frysinger
2016-03-02 18:18 Mike Frysinger
2015-09-01 18:56 Tobias Klausmann
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=1510999232.5fc39f340611550bdc06c27983d6f60d7aba3ae0.slyfox@gentoo \
--to=slyfox@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