Re: [RFC][PATCH 0/4] malloc_info: minor fixes and improvements [BZ #17039]

[Carlos O'Donell <carlos at redhat dot com>]

On 04/30/2018 05:00 PM, Ken Milmore wrote:
> I've been looking into the malloc_info() function as a way of
> examining heap fragmentation of running programs. Unfortunately, it
> has a couple of annoying problems which have both been mentioned
> already in BZ #17039.

Overall I'm excited to see someone looking at this and your changes
look like they go in the right direction.

Have you given a look through the "Contribution Checklist?"
https://sourceware.org/glibc/wiki/Contribution%20checklist

Do you have a copyright assignment with the FSF?

We can actually probably accept your changes without an assignment
because they are ~15 lines, but that's the limit, we would not be
able to accept your totally awesome testcase without some kind of
assignment.

Everything else on the contribution checklist is fairly straight
forward stuff and we can help with that.

The FSF does digital assignments now around the world, so a copyright
assignment should be really quick. I usually recommend a future's assignment
if you are at all interested in continuing to contribute patches here and
there to the project.

http://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future

Please feel free to contact me off-list if you have any questions about
how to fill out the form.

If you're wondering why we go to the trouble:
https://www.gnu.org/licenses/why-assign.en.html

-- 
Cheers,
Carlos.