From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/jemalloc/
Date: Wed, 13 Nov 2019 07:39:47 +0000 (UTC) [thread overview]
Message-ID: <1573630749.cd37a856ca2d7872205875d7a9ac7ee0f8d31bcf.ago@gentoo> (raw)
commit: cd37a856ca2d7872205875d7a9ac7ee0f8d31bcf
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 13 07:39:09 2019 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Wed Nov 13 07:39:09 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cd37a856
dev-libs/jemalloc: ppc stable wrt bug #699944
Package-Manager: Portage-2.3.76, Repoman-2.3.16
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
dev-libs/jemalloc/jemalloc-5.2.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/jemalloc/jemalloc-5.2.1.ebuild b/dev-libs/jemalloc/jemalloc-5.2.1.ebuild
index f8cbd763e64..2c343468d50 100644
--- a/dev-libs/jemalloc/jemalloc-5.2.1.ebuild
+++ b/dev-libs/jemalloc/jemalloc-5.2.1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/jemalloc/jemalloc/releases/download/${PV}/${P}.tar.b
LICENSE="BSD"
SLOT="0/2"
-KEYWORDS="~alpha ~amd64 ~arm arm64 ~hppa ~ia64 ~ppc ~ppc64 ~s390 ~x86 ~amd64-linux ~x86-linux ~x64-macos ~x64-solaris"
+KEYWORDS="~alpha ~amd64 ~arm arm64 ~hppa ~ia64 ppc ~ppc64 ~s390 ~x86 ~amd64-linux ~x86-linux ~x64-macos ~x64-solaris"
IUSE="debug hardened lazy-lock prof static-libs stats xmalloc"
HTML_DOCS=( doc/jemalloc.html )
PATCHES=( "${FILESDIR}/${PN}-5.2.0-gentoo-fixups.patch" )
next reply other threads:[~2019-11-13 7:39 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 7:39 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-25 0:01 [gentoo-commits] repo/gentoo:master commit in: dev-libs/jemalloc/ Joshua Kinard
2022-10-24 6:02 Joonas Niilola
2022-10-24 6:02 Joonas Niilola
2022-10-21 14:52 Arthur Zamarin
2022-10-21 14:52 Arthur Zamarin
2022-10-21 14:52 Arthur Zamarin
2022-10-21 14:52 Arthur Zamarin
2022-10-21 14:52 Arthur Zamarin
2022-10-21 12:02 Joonas Niilola
2022-10-21 12:02 Joonas Niilola
2022-09-26 7:31 Michał Górny
2022-09-19 6:42 Michał Górny
2022-08-30 16:05 Arthur Zamarin
2022-08-30 7:17 Arthur Zamarin
2022-07-31 11:08 Agostino Sarubbo
2022-07-30 14:31 Arthur Zamarin
2022-07-30 12:35 Arthur Zamarin
2022-07-30 9:51 Arthur Zamarin
2022-07-30 9:51 Arthur Zamarin
2022-07-30 7:05 Joonas Niilola
2022-07-30 7:05 Joonas Niilola
2022-07-03 17:09 James Le Cuirot
2022-07-02 7:02 Jakov Smolić
2022-07-01 6:16 Arthur Zamarin
2022-07-01 6:10 Arthur Zamarin
2022-07-01 6:10 Arthur Zamarin
2022-07-01 5:18 Arthur Zamarin
2022-06-30 22:12 Yixun Lan
2022-06-30 21:47 Sam James
2022-06-30 5:55 Joonas Niilola
2022-06-30 5:55 Joonas Niilola
2022-05-28 20:42 Jakov Smolić
2022-05-14 5:32 WANG Xuerui
2022-05-05 9:51 WANG Xuerui
2022-01-23 7:41 Joonas Niilola
2022-01-20 11:47 Sam James
2022-01-18 22:16 Sam James
2022-01-18 12:26 Sam James
2022-01-15 22:01 Sam James
2022-01-15 22:01 Sam James
2022-01-15 10:25 Jakov Smolić
2022-01-15 10:25 Jakov Smolić
2021-09-20 20:54 James Le Cuirot
2021-03-21 10:19 Sergei Trofimovich
2020-09-01 9:50 Yixun Lan
2019-12-08 4:50 Matt Turner
2019-11-21 17:17 Sergei Trofimovich
2019-11-14 11:55 Agostino Sarubbo
2019-11-13 16:07 Agostino Sarubbo
2019-11-13 8:43 Agostino Sarubbo
2019-11-13 8:16 Agostino Sarubbo
2019-11-13 7:48 Agostino Sarubbo
2019-11-12 17:47 Aaron Bauman
2019-08-07 20:26 Thomas Deutschmann
2019-08-07 20:26 Thomas Deutschmann
2018-12-12 12:57 Mikle Kolyada
2018-08-23 0:22 Thomas Deutschmann
2018-05-28 6:56 Jory Pratt
2018-04-09 15:01 Lars Wendler
2018-04-09 14:23 Lars Wendler
2017-12-03 17:50 Fabian Groffen
2017-08-29 14:14 Guilherme Amadio
2016-12-14 0:40 Jory Pratt
2016-07-17 8:15 Jory Pratt
2015-11-28 16:23 Jory Pratt
2015-11-26 21:58 Jory Pratt
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=1573630749.cd37a856ca2d7872205875d7a9ac7ee0f8d31bcf.ago@gentoo \
--to=ago@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