Re: [gentoo-dev] Re: Gentoo Bugday

2013-02-26 Thread Alec Warner
On Tue, Feb 26, 2013 at 7:14 PM, Michael Palimaka wrote: > On 27/02/2013 11:39, Pavlos Ratis wrote: >> >> Hello everyone, >> >> I would like to announce you a new try to 'revive' the Bugday event. >> As most of the open source projects have their own bugday, I thought >> it would be great to have

[gentoo-dev] Re: Evaluating a new malloc()

2013-02-26 Thread Ryan Hill
On Tue, 26 Feb 2013 08:33:44 -0500 Richard Yao wrote: > With that said, what do people think? I think I see a lot of our upstream bug reports being closed as invalid/unsupported. I think that if upstreams wanted to use jemalloc they would just do so. If they don't then obviously what they have

[gentoo-dev] Re: Gentoo Bugday

2013-02-26 Thread Michael Palimaka
On 27/02/2013 11:39, Pavlos Ratis wrote: Hello everyone, I would like to announce you a new try to 'revive' the Bugday event. As most of the open source projects have their own bugday, I thought it would be great to have this event back. For those who don't know, its a monthly 24h event that ta

Re: [gentoo-dev] Gentoo Bugday

2013-02-26 Thread Paweł Hajdan, Jr.
On 2/26/13 4:39 PM, Pavlos Ratis wrote: > I would like to announce you a new try to 'revive' the Bugday event. This is excellent! Thank you for your work on this. > I have listed some maintainer-wanted and maintainer-need bugs and > Bugzilla admins also re-enabled the bugday flag. I would like to

[gentoo-dev] Gentoo Bugday

2013-02-26 Thread Pavlos Ratis
Hello everyone, I would like to announce you a new try to 'revive' the Bugday event. As most of the open source projects have their own bugday, I thought it would be great to have this event back. For those who don't know, its a monthly 24h event that takes place in #gentoo-bugs. Its goal is to c

Re: [gentoo-dev] Evaluating a new malloc()

2013-02-26 Thread William Hubbs
On Tue, Feb 26, 2013 at 11:10:09AM -0800, Matt Turner wrote: > On Tue, Feb 26, 2013 at 8:35 AM, Alec Warner wrote: > > In terms of 'following Gentoo policy.' We encourage packages to be as > > close to upstream as possible. I cannot fathom why when you basically > > find a performance bug in mallo

[gentoo-dev] Last rites: app-emacs/yow

2013-02-26 Thread Ulrich Mueller
# Ulrich Müller (26 Feb 2013) # Declared as obsolete by upstream. Use fortune.el with # the zippy file from games-misc/fortune-mod instead. # Masked for removal in 30 days, bug #459358. app-emacs/yow

Re: [gentoo-dev] Evaluating a new malloc()

2013-02-26 Thread Matt Turner
On Tue, Feb 26, 2013 at 1:37 PM, Maciej Mrozowski wrote: > On Tuesday 26 of February 2013 11:44:31 Rich Freeman wrote: >> On Tue, Feb 26, 2013 at 11:35 AM, Alec Warner wrote: >> > I see a *HUGE* reason. glibc ships with ptmalloc. If you think they >> > should use jemalloc, talk to them. Don't jus

Re: [gentoo-dev] Evaluating a new malloc()

2013-02-26 Thread Jeff Horelick
On 26 February 2013 16:37, Maciej Mrozowski wrote: > On Tuesday 26 of February 2013 11:44:31 Rich Freeman wrote: > > On Tue, Feb 26, 2013 at 11:35 AM, Alec Warner > wrote: > > > I see a *HUGE* reason. glibc ships with ptmalloc. If you think they > > > should use jemalloc, talk to them. Don't jus

Re: [gentoo-dev] Evaluating a new malloc()

2013-02-26 Thread Maciej Mrozowski
On Tuesday 26 of February 2013 11:44:31 Rich Freeman wrote: > On Tue, Feb 26, 2013 at 11:35 AM, Alec Warner wrote: > > I see a *HUGE* reason. glibc ships with ptmalloc. If you think they > > should use jemalloc, talk to them. Don't just do it in Gentoo. > > Certainly I think it would be far more

Re: [gentoo-dev] Evaluating a new malloc()

2013-02-26 Thread Matt Turner
On Tue, Feb 26, 2013 at 8:35 AM, Alec Warner wrote: > In terms of 'following Gentoo policy.' We encourage packages to be as > close to upstream as possible. I cannot fathom why when you basically > find a performance bug in malloc, you start a thread on the list about > replacing it; as opposed to

Re: [gentoo-dev] Evaluating a new malloc()

2013-02-26 Thread Rich Freeman
On Tue, Feb 26, 2013 at 11:35 AM, Alec Warner wrote: > I see a *HUGE* reason. glibc ships with ptmalloc. If you think they > should use jemalloc, talk to them. Don't just do it in Gentoo. Certainly I think it would be far more productive to talk to the glibc maintainers first. However, nothing p

Re: [gentoo-dev] Evaluating a new malloc()

2013-02-26 Thread Mike Gilbert
On Tue, Feb 26, 2013 at 8:33 AM, Richard Yao wrote: > Unless a significant issue is found in jemalloc itself, I do not see any > reason to continue using glibc's ptmalloc over jemalloc. As far as I > know, FreeBSD, NetBSD, Facebook and others are using jemalloc, so I > expect that no significant i

Re: [gentoo-dev] Evaluating a new malloc()

2013-02-26 Thread Alec Warner
On Tue, Feb 26, 2013 at 5:33 AM, Richard Yao wrote: > The Blender project found some fairly remarkable discrepancies between > what their software actually used and what glibc's ptmalloc allocated: > > http://www.sintel.org/development/memory-jemalloc/ > > Results such as these led Blender and oth

Re: [gentoo-dev] [RFC/PATCH] A cleaner API for virtualx.eclass

2013-02-26 Thread Michał Górny
On Tue, 12 Feb 2013 18:42:28 +0100 ""Paweł Hajdan, Jr."" wrote: > On 2/11/13 11:14 PM, Michał Górny wrote: > > My patches introduce a single wrapper with argv-as-parameter syntax. > > That is, the fore-mentioned example would look like: > > > > virtualx run_tests --foo > > Maybe we can just

Re: [gentoo-dev] Evaluating a new malloc()

2013-02-26 Thread Florian Philipp
Am 26.02.2013 14:52, schrieb Richard Yao: > On 02/26/2013 08:48 AM, Alexander Berntsen wrote: >> On 26/02/13 14:33, Richard Yao wrote: >>> The Blender project found some fairly remarkable discrepancies >>> between what their software actually used and what glibc's ptmalloc >>> allocated >> Have the

Re: [gentoo-dev] Evaluating a new malloc()

2013-02-26 Thread Richard Yao
On 02/26/2013 08:48 AM, Alexander Berntsen wrote: > On 26/02/13 14:33, Richard Yao wrote: >> The Blender project found some fairly remarkable discrepancies >> between what their software actually used and what glibc's ptmalloc >> allocated > Have they filed a bug? > I don't know. You should ask t

Re: [gentoo-dev] Evaluating a new malloc()

2013-02-26 Thread Alexander Berntsen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 26/02/13 14:33, Richard Yao wrote: > The Blender project found some fairly remarkable discrepancies > between what their software actually used and what glibc's ptmalloc > allocated Have they filed a bug? - -- Alexander alexan...@plaimi.net http:

Re: [gentoo-dev] Evaluating a new malloc()

2013-02-26 Thread Richard Yao
On 02/26/2013 08:35 AM, Diego Elio Pettenò wrote: > On 26/02/2013 14:33, Richard Yao wrote: >> Results such as these led Blender and others (e.g. Chrome/Chromium, >> Firefox, Thunderbird) to bundle private versions of jemalloc. This >> bundling situation violates our policy against bundled librarie

Re: [gentoo-dev] Evaluating a new malloc()

2013-02-26 Thread Diego Elio Pettenò
On 26/02/2013 14:33, Richard Yao wrote: > Results such as these led Blender and others (e.g. Chrome/Chromium, > Firefox, Thunderbird) to bundle private versions of jemalloc. This > bundling situation violates our policy against bundled libraries. The > maintainers could just patch their software to

[gentoo-dev] Evaluating a new malloc()

2013-02-26 Thread Richard Yao
The Blender project found some fairly remarkable discrepancies between what their software actually used and what glibc's ptmalloc allocated: http://www.sintel.org/development/memory-jemalloc/ Results such as these led Blender and others (e.g. Chrome/Chromium, Firefox, Thunderbird) to bundle priv

Re: [gentoo-dev] RFC: Gentoo GPG key policies

2013-02-26 Thread grozin
Hello *, I am stuck and have many questions. [In the process of becoming a dev, I've generated a gpg key, of course. It vwas on an old notebook. When I switched to a newer notebook, I forgot to copy it, because I don't use gpg regularly. No risk that it became known - the disk was re-partitio