public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jason Zaman" <perfinion@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/google-perftools/
Date: Fri, 15 Dec 2017 09:36:36 +0000 (UTC)	[thread overview]
Message-ID: <1513330588.ec1f174ef317159285dc438358be739ecd0355e3.perfinion@gentoo> (raw)

commit:     ec1f174ef317159285dc438358be739ecd0355e3
Author:     Jason Zaman <perfinion <AT> gentoo <DOT> org>
AuthorDate: Fri Dec 15 09:35:54 2017 +0000
Commit:     Jason Zaman <perfinion <AT> gentoo <DOT> org>
CommitDate: Fri Dec 15 09:36:28 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ec1f174e

dev-util/google-perftools: amd64 stable

Gentoo-bug: 640330
Package-Manager: Portage-2.3.13, Repoman-2.3.3

 dev-util/google-perftools/google-perftools-2.6.2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-util/google-perftools/google-perftools-2.6.2.ebuild b/dev-util/google-perftools/google-perftools-2.6.2.ebuild
index 2693c942343..915b1349424 100644
--- a/dev-util/google-perftools/google-perftools-2.6.2.ebuild
+++ b/dev-util/google-perftools/google-perftools-2.6.2.ebuild
@@ -17,7 +17,7 @@ SLOT="0/4"
 # linux x86/amd64/ppc/ppc64/arm
 # OSX ppc/amd64
 # AIX ppc/ppc64
-KEYWORDS="-* ~amd64 ~arm ~arm64 ppc ppc64 x86 ~x86-fbsd ~amd64-linux ~x86-linux"
+KEYWORDS="-* amd64 ~arm ~arm64 ppc ppc64 x86 ~x86-fbsd ~amd64-linux ~x86-linux"
 IUSE="largepages +debug minimal optimisememory test static-libs"
 
 DEPEND="sys-libs/libunwind"


             reply	other threads:[~2017-12-15  9:36 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15  9:36 Jason Zaman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-20 20:11 [gentoo-commits] repo/gentoo:master commit in: dev-util/google-perftools/ Arthur Zamarin
2024-06-20 20:11 Arthur Zamarin
2024-06-20 20:10 Arthur Zamarin
2024-06-20 20:10 Arthur Zamarin
2024-06-20 18:06 Sam James
2024-06-19 19:43 Arthur Zamarin
2024-03-02 22:16 Bernard Cafarelli
2024-03-02 13:22 Arthur Zamarin
2024-02-24 10:20 Bernard Cafarelli
2024-02-17 14:48 Sam James
2024-02-15 20:50 Bernard Cafarelli
2024-02-15 20:03 Sam James
2024-02-15 20:03 Sam James
2024-02-15 18:34 Jakov Smolić
2024-02-15 18:34 Jakov Smolić
2024-02-15 13:11 Bernard Cafarelli
2022-09-02 21:28 Sam James
2022-07-15  1:32 Sam James
2021-10-27 22:54 Sam James
2021-10-27 22:47 Sam James
2021-10-27 22:47 Sam James
2021-10-27 22:35 Sam James
2021-10-27 22:35 Sam James
2021-10-27 22:33 Sam James
2021-10-27  5:37 Sam James
2021-10-27  5:34 Sam James
2021-07-11 22:02 Marek Szuba
2021-07-11 22:02 Marek Szuba
2021-06-15 18:47 Georgy Yakovlev
2020-08-21  6:13 Georgy Yakovlev
2020-08-21  3:12 Georgy Yakovlev
2020-06-06 17:38 Agostino Sarubbo
2020-06-06 17:34 Agostino Sarubbo
2020-06-06 17:32 Agostino Sarubbo
2020-06-06 17:29 Agostino Sarubbo
2020-06-06 17:27 Agostino Sarubbo
2020-06-06  8:33 Georgy Yakovlev
2020-06-06  7:36 Georgy Yakovlev
2020-04-15  4:29 Georgy Yakovlev
2020-04-15  2:42 Georgy Yakovlev
2020-04-15  2:42 Georgy Yakovlev
2020-02-09 13:14 David Seifert
2019-04-25  3:52 Aaron Bauman
2018-10-14 11:40 Pacho Ramos
2018-10-14 10:18 Pacho Ramos
2018-01-23  5:58 Markus Meier
2017-12-19  3:09 Lars Wendler
2017-12-19  3:09 Lars Wendler
2017-12-09 14:54 Sergei Trofimovich
2017-12-08 21:58 Thomas Deutschmann
2017-12-01  5:08 Zac Medico
2017-08-10 15:49 Guilherme Amadio
2017-07-30 20:31 Patrick McLean
2017-07-30 20:31 Patrick McLean
2017-07-29 23:24 Patrick McLean
2017-07-07 18:15 Alexis Ballier
2017-02-15 23:14 Michael Weber
2016-12-29  4:12 Göktürk Yüksek
2016-09-27  7:57 Michał Górny
2016-06-08  6:29 Yixun Lan
2015-09-21  4:58 Jeroen Roovers
2015-09-01 19:31 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=1513330588.ec1f174ef317159285dc438358be739ecd0355e3.perfinion@gentoo \
    --to=perfinion@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