public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-qt/linguist-tools/
Date: Wed,  9 Mar 2016 04:12:42 +0000 (UTC)	[thread overview]
Message-ID: <1457496715.466741cdbe224e18bfb1fc8182da63205f950efd.jer@gentoo> (raw)

commit:     466741cdbe224e18bfb1fc8182da63205f950efd
Author:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Wed Mar  9 03:50:01 2016 +0000
Commit:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Wed Mar  9 04:11:55 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=466741cd

dev-qt/linguist-tools: Stable for HPPA PPC64 (bug #569924).

Package-Manager: portage-2.2.27
RepoMan-Options: --ignore-arches

 dev-qt/linguist-tools/linguist-tools-5.5.1-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-qt/linguist-tools/linguist-tools-5.5.1-r1.ebuild b/dev-qt/linguist-tools/linguist-tools-5.5.1-r1.ebuild
index 96c3525..85e183d 100644
--- a/dev-qt/linguist-tools/linguist-tools-5.5.1-r1.ebuild
+++ b/dev-qt/linguist-tools/linguist-tools-5.5.1-r1.ebuild
@@ -9,7 +9,7 @@ inherit qt5-build
 DESCRIPTION="Tools for working with Qt translation data files"
 
 if [[ ${QT5_BUILD_TYPE} == release ]]; then
-	KEYWORDS="amd64 ~arm ~arm64 ~hppa ~ppc64 ~x86"
+	KEYWORDS="amd64 ~arm ~arm64 hppa ppc64 ~x86"
 fi
 
 IUSE="qml"


             reply	other threads:[~2016-03-09  4:13 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09  4:12 Jeroen Roovers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-03 19:06 [gentoo-commits] repo/gentoo:master commit in: dev-qt/linguist-tools/ Arthur Zamarin
2024-04-03 18:48 Arthur Zamarin
2024-01-31 22:47 Ionen Wolkens
2023-11-06  7:14 Arthur Zamarin
2023-07-12 23:39 Sam James
2023-07-12  1:13 Sam James
2023-04-25  9:42 Arthur Zamarin
2022-12-05 19:45 Arthur Zamarin
2022-07-04 17:58 Arthur Zamarin
2022-07-02 12:54 Arthur Zamarin
2022-07-02 11:02 Arthur Zamarin
2022-06-19 22:45 Sam James
2022-06-19 22:45 Sam James
2022-06-19  5:30 Sam James
2022-06-19  5:29 Sam James
2022-06-18 15:39 Sam James
2022-06-13 21:18 Sam James
2022-06-09 14:13 Andreas Sturmlechner
2022-05-19  5:08 WANG Xuerui
2022-04-17 18:18 Sam James
2022-04-12 18:45 Arthur Zamarin
2021-10-17  0:29 Sam James
2021-10-17  0:27 Sam James
2021-09-30 18:21 Sam James
2021-09-30 18:15 Sam James
2021-09-08 16:55 Andreas Sturmlechner
2020-05-30 19:33 Sergei Trofimovich
2020-01-27 10:48 Mikle Kolyada
2020-01-13 19:50 Sergei Trofimovich
2019-04-28 21:36 Anthony G. Basile
2018-12-07 20:07 Sergei Trofimovich
2018-09-07 23:46 Sergei Trofimovich
2018-08-22  1:21 Mikle Kolyada
2018-08-17 21:12 Sergei Trofimovich
2018-03-21  7:25 Sergei Trofimovich
2018-03-13 19:51 Michał Górny
2017-07-15  5:16 Markus Meier
2017-03-17  7:47 Jeroen Roovers
2017-01-02 19:03 Markus Meier
2016-10-13  9:41 Agostino Sarubbo
2016-08-23 19:43 Markus Meier
2016-08-15  5:56 Jeroen Roovers
2016-03-27 16:47 Agostino Sarubbo
2016-03-24  5:53 Markus Meier
2016-03-05 22:20 Mikle Kolyada
2015-09-21  4:58 Jeroen Roovers
2015-08-23  9:24 Jeroen Roovers

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=1457496715.466741cdbe224e18bfb1fc8182da63205f950efd.jer@gentoo \
    --to=jer@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