This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] Fixes TLS performance degradation after dlopen
- From: Philipp Trommler <Philipp dot Trommler at mailbox dot tu-dresden dot de>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: Chris Metcalf <cmetcalf at mellanox dot com>, libc-alpha at sourceware dot org
- Date: Wed, 15 Jun 2016 11:07:44 +0000
- Subject: Re: [PATCH] Fixes TLS performance degradation after dlopen
- Authentication-results: sourceware.org; auth=none
- References: <1465309688 dot 1188 dot 19 dot camel at mailbox dot tu-dresden dot de> <6182e3d1-7f52-72ee-5da0-caa36dbb1ac7 at mellanox dot com> <45e4c835-0294-df72-df73-45e271c6137c at redhat dot com> <1465893127 dot 1113 dot 2 dot camel at mailbox dot tu-dresden dot de> <45198f15-45c7-f522-18f9-fe320a071417 at redhat dot com>
Zitat von Carlos O'Donell <email@example.com>:
On 06/14/2016 04:32 AM, Philipp Trommler wrote:
Do you have copyright assignments with the FSF in place for glibc? This is
required to allow you to contribute code to the glibc project.
Please see the "Contribution Checklist":
No, I do not have a copyright assignment with the FSF yet. Am I
right that in
order to get one I have to fill out this
b.git/plain/doc/Copyright/request-assign.changes) form and send it to
Yes. That form limits you to just the changes you are making today.
Be aware that you will have to go through the process all over again
for any different future changes.
The alternative is a futures assignment for the project which covers
all present and future contributions to the project e.g.
Which need be done only once to allow you to contribute to the project
from here on out.
Thanks, I'll fill that out and give you feedback when I get a response.