String routines for ARM and licensing

[Michael Hope]

Thank you for your feedback.  I had a quick look at the architecture
specific mem* and str* routines[1] and see what you mean - all except
vax have FSF-held copyright.

I like the idea of an add-on to get us up and going quickly while we
tidy up the assignment issues.  We'll talk further internally and see
what we can come up with.

-- Michael

[1] https://wiki.linaro.org/WorkingGroups/ToolChain/StringRoutines#Use%20in%20EGLIBC

On Fri, Aug 13, 2010 at 8:18 PM, Roland McGrath <roland@redhat.com> wrote:
> In general, all contributions to glibc require an FSF copyright
> assignment.  We do not include code with copyright owners other than
> FSF except in special situations.  Intel supplies optimized string
> functions for their new processors too, and they have assigned
> copyright to FSF for those contributions.  You can too.
>
> Note that it is easy to produce a glibc add-on that supplies new
> sysdeps/ file implementations such as these.  If you won't meet the
> requirements to contribute your code to glibc directly, you can
> distribute it separately and encourage ARM users and system builders
> to build glibc with your add-on.  That is also an easy way to make it
> available for others to test and use before you have worked out the
> details about contributing it to glibc or not.
>
> Also note that ARM is maintained in libc-ports, and the correct
> mailing list to discuss ARM glibc technical details with the ARM port
> maintainers is <libc-ports@sourceware.org>, not this mailing list.
>
>
> Thanks,
> Roland
>