This is the mail archive of the
mailing list for the glibc project.
Re: malloc: performance improvements and bugfixes
- From: Manuel LÃpez-IbÃÃez <lopezibanez at gmail dot com>
- To: JÃrn Engel <joern at purestorage dot com>, Florian Weimer <fweimer at redhat dot com>, Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>, Paul Eggert <eggert at cs dot ucla dot edu>, "GNU C. Library" <libc-alpha at sourceware dot org>, Joern Engel <joern at purestorage dot org>
- Date: Wed, 27 Jan 2016 20:45:57 +0000
- Subject: Re: malloc: performance improvements and bugfixes
- Authentication-results: sourceware.org; auth=none
- References: <1453767942-19369-1-git-send-email-joern at purestorage dot com> <56A6C2E4 dot 7050508 at cs dot ucla dot edu> <20160126010058 dot GI26397 at Sligo dot logfs dot org> <CAAHN_R3=C476ADoAD0cOPJaw4idGFXzcO3_dj1GLfssehhdsvQ at mail dot gmail dot com> <20160126024437 dot GA5745 at Sligo dot logfs dot org> <20160126032122 dot GC5745 at Sligo dot logfs dot org> <20160126062208 dot GA14840 at vapier dot lan> <20160126075358 dot GD5745 at Sligo dot logfs dot org> <56A7420D dot 8010802 at redhat dot com> <20160126170455 dot GF5745 at Sligo dot logfs dot org> <20160126175753 dot GC14840 at vapier dot lan>
JÃrn (and others),
Judging from similar discussions in the GCC list:
I would strongly advise to stop discussing this here and contact the
copyright-clerk of the FSF and expose your case: "I want to contribute to GNU
libc, but I don't want to assign copyright because of X, Y, and Z. What can I do?"
1) As the thread in GCC shows, almost every contributor to any GNU project
don't know or are completely wrong about the details. At most, they can tell
you their personal case, however, the FSF changes their processes with respect
to legal changes, thus personal experience is of limited value.
2) The process is very individualized. It depends on where you live, where you
work, how much you want to contribute, etc. Only the FSF clerk (who I guess is
a lawyer or has access to a lawyer) knows all the fine details.
3) The FSF is very flexible and will try to personalize the process to your
circumstances and desires. So explain them in detail what are your worries and
questions. In my first CA, I changed some parts of the document to please my
university (whose lawyers had to sign it), and the FSF was ok with it.
As I said in that thread, "the process is overly complex, obscure, confusing
and slow. It does not seem that it needs to be so. It is scaring away potential
contributors and slowing down GCC development." and "It would be
extremely useful if anyone that feels confident on the subject wrote a
FAQ-like document in the wiki that we could use as a reference for the
However, only the FSF can fix this, any discussion here about the what, the how
or the why is pointless. (Yet, more than 5 years have passed since the above
discussion and the situation has not improved. I firmly believe that the CA is
the number one hurdle for contributing to GCC, more than the GPLv3 or the code