This is the mail archive of the
mailing list for the newlib project.
Re: CodeSourcery's licensing of newlib files
- From: Ralf Corsepius <ralf dot corsepius at rtems dot org>
- To: "Jonathan S. Shapiro" <shap at eros-os dot org>
- Cc: "newlib at sourceware dot org" <newlib at sourceware dot org>
- Date: Thu, 24 Oct 2013 17:46:09 +0200
- Subject: Re: CodeSourcery's licensing of newlib files
- Authentication-results: sourceware.org; auth=none
- References: <52002514-06af832aa02dd5da957c6e7accaca7d4 at pmq1v dot m5r2 dot onet> <CADtm3G7S6Pjch8BQ+P8THt+8kfFX30xeswR6NT2CjifegVWwqg at mail dot gmail dot com> <5268CFAA dot 5060906 at rtems dot org> <CAAP=3QPdCuTBwnQpem4HK7DVNpp-Co3HkD=rxSfgjE4yscjsJg at mail dot gmail dot com>
On 10/24/2013 05:06 PM, Jonathan S. Shapiro wrote:
On Thu, Oct 24, 2013 at 12:43 AM, Ralf Corsepius
On 10/23/2013 10:09 PM, Gregory Fong wrote:
On Wed, Oct 23, 2013 at 6:03 AM, freddie_chopin <email@example.com>
Can they attach sth like that to newlib's files?
Yes, that's permitted under the BSD license.
Correct, but it means their changes can not be applied to sourceware.org's
If by "they" you mean "SourceWare", then that's incorrect. SourceWare can
sign appropriate releases and donate their code.
No, I mean CodeSourcery.
CS can add their Licensing to their newlib-fork, but as their changes
are not BSD compatible they can not be applied to Sourceware's newlib,
because Sourceware's newlib is supposed to be BSD-compatible.