mirrors/tinycc
1
0
Fork 0
mirror of https://github.com/frida/tinycc synced 2024-11-28 02:29:38 +03:00
Code Issues Packages Projects Releases Wiki Activity
d0db21757a
tinycc/RELICENSING

61 lines
2.6 KiB
Plaintext
Raw Normal View History

Relicensing TinyCC It has been discussed on the list whether it would be good to relicense TinyCC under a more permissive BSD-like license. The discussion started here: http://lists.gnu.org/archive/html/tinycc-devel/2013-04/msg00052.html Opinions varied but mostly were positive so it appears to be worth to start the process and see how far we can get. For that purpose I've committed a new file RELICENSING with the suggested new license clause and a list for people to confirm their agreement (or disagreement). If you have contributed to TinyCC in the past, in particular if you are one of the copyright owners for an entire file, please add yourself to that file (rsp. replace the question mark) and commit the change to the "mob" brancn with log message: Relicensing TinyCC Thanks.
2013-05-06 01:45:51 +04:00
Relicensing TinyCC
------------------
The authors listed below hereby confirm their agreement to relicense TinyCC
including their past contributions under the following terms:
* Permission is hereby granted, free of charge, to any person obtaining a copy
* of this software and associated documentation files (the "Software"), to deal
* in the Software without restriction, including without limitation the rights
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
* copies of the Software, and to permit persons to whom the Software is
* furnished to do so, subject to the following conditions:
*
* The above copyright notice and this permission notice shall be included in
* all copies or substantial portions of the software.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
* THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
* THE SOFTWARE.
Author (name) I agree (YES/NO) Files/Features (optional)
------------------------------------------------------------------------------
Relicensing TinyCC. I've been sending a lot of mails out asking contributors if they approve the license change, so I'm adding the ones who reply here.
2015-07-29 16:03:37 +03:00
Adam Sampson YES makefiles
Convert some lines from ISO-8859-1 to UTF-8. perl -i -pe 'use Text::Iconv; $c1 = Text::Iconv->new("utf-8", "utf-8"); $c2 = Text::Iconv->new("iso-8859-1", "utf-8"); if (!$c1->convert($_)) { $_ = $c2->convert($_); }' \ `find * -type f`
2015-03-09 01:07:50 +03:00
Daniel Glöckner NO arm-gen.c
Daniel Glöckner YES not arm-gen.c
Relicensing TinyCC. I've been sending a lot of mails out asking contributors if they approve the license change, so I'm adding the ones who reply here.
2015-07-29 16:03:37 +03:00
Edmund Grimley Evans YES arm64
Relicensing TinyCC
2013-05-23 12:40:12 +04:00
Fabrice Bellard YES original author
Convert some lines from ISO-8859-1 to UTF-8. perl -i -pe 'use Text::Iconv; $c1 = Text::Iconv->new("utf-8", "utf-8"); $c2 = Text::Iconv->new("iso-8859-1", "utf-8"); if (!$c1->convert($_)) { $_ = $c2->convert($_); }' \ `find * -type f`
2015-03-09 01:07:50 +03:00
Frédéric Féret YES x86 64/16 bit asm
Relicensing TinyCC It has been discussed on the list whether it would be good to relicense TinyCC under a more permissive BSD-like license. The discussion started here: http://lists.gnu.org/archive/html/tinycc-devel/2013-04/msg00052.html Opinions varied but mostly were positive so it appears to be worth to start the process and see how far we can get. For that purpose I've committed a new file RELICENSING with the suggested new license clause and a list for people to confirm their agreement (or disagreement). If you have contributed to TinyCC in the past, in particular if you are one of the copyright owners for an entire file, please add yourself to that file (rsp. replace the question mark) and commit the change to the "mob" brancn with log message: Relicensing TinyCC Thanks.
2013-05-06 01:45:51 +04:00
grischka YES tccpe.c
Adding two more people to the RELICENSING file. They also responded to my mail with a YES.
2015-07-31 23:56:23 +03:00
Henry Kroll YES
Joe Soroka YES
Relicensing TinyCC. I've been sending a lot of mails out asking contributors if they approve the license change, so I'm adding the ones who reply here.
2015-07-29 16:03:37 +03:00
Kirill Smelkov YES
mingodad YES
Pip Cet YES
Relicensing TinyCC
2013-05-06 01:55:16 +04:00
Shinichiro Hamaji YES x86_64-gen.c
Relicensing TinyCC
2015-07-29 16:24:56 +03:00
Vincent Lefèvre YES
Relicensing TinyCC
2013-05-06 01:51:58 +04:00
Thomas Preud'homme YES arm-gen.c
Convert some lines from ISO-8859-1 to UTF-8. perl -i -pe 'use Text::Iconv; $c1 = Text::Iconv->new("utf-8", "utf-8"); $c2 = Text::Iconv->new("iso-8859-1", "utf-8"); if (!$c1->convert($_)) { $_ = $c2->convert($_); }' \ `find * -type f`
2015-03-09 01:07:50 +03:00
Timo VJ Lähde (Timppa) ? tiny_libmaker.c
Relicensing TinyCC It has been discussed on the list whether it would be good to relicense TinyCC under a more permissive BSD-like license. The discussion started here: http://lists.gnu.org/archive/html/tinycc-devel/2013-04/msg00052.html Opinions varied but mostly were positive so it appears to be worth to start the process and see how far we can get. For that purpose I've committed a new file RELICENSING with the suggested new license clause and a list for people to confirm their agreement (or disagreement). If you have contributed to TinyCC in the past, in particular if you are one of the copyright owners for an entire file, please add yourself to that file (rsp. replace the question mark) and commit the change to the "mob" brancn with log message: Relicensing TinyCC Thanks.
2013-05-06 01:45:51 +04:00
TK ? tcccoff.c c67-gen.c
Relicensing TinyCC. I've been sending a lot of mails out asking contributors if they approve the license change, so I'm adding the ones who reply here.
2015-07-29 16:03:37 +03:00
Urs Janssen YES
waddlesplash YES
Add note about native Windows bootstrap using Cygwin.
2017-02-23 08:45:26 +03:00
Christian Jullien YES Windows Cygwin build and tests
Relicensing TinyCC It has been discussed on the list whether it would be good to relicense TinyCC under a more permissive BSD-like license. The discussion started here: http://lists.gnu.org/archive/html/tinycc-devel/2013-04/msg00052.html Opinions varied but mostly were positive so it appears to be worth to start the process and see how far we can get. For that purpose I've committed a new file RELICENSING with the suggested new license clause and a list for people to confirm their agreement (or disagreement). If you have contributed to TinyCC in the past, in particular if you are one of the copyright owners for an entire file, please add yourself to that file (rsp. replace the question mark) and commit the change to the "mob" brancn with log message: Relicensing TinyCC Thanks.
2013-05-06 01:45:51 +04:00
------------------------------------------------------------------------------
Please add yourself to the list above (rsp. replace the question mark)
typo in RELICENSING
2015-07-29 16:29:22 +03:00
and (after fetching the latest version) commit to the "mob" branch with
Relicensing TinyCC It has been discussed on the list whether it would be good to relicense TinyCC under a more permissive BSD-like license. The discussion started here: http://lists.gnu.org/archive/html/tinycc-devel/2013-04/msg00052.html Opinions varied but mostly were positive so it appears to be worth to start the process and see how far we can get. For that purpose I've committed a new file RELICENSING with the suggested new license clause and a list for people to confirm their agreement (or disagreement). If you have contributed to TinyCC in the past, in particular if you are one of the copyright owners for an entire file, please add yourself to that file (rsp. replace the question mark) and commit the change to the "mob" brancn with log message: Relicensing TinyCC Thanks.
2013-05-06 01:45:51 +04:00
commit message:
Relicensing TinyCC
Thanks.
Reference in New Issue Copy Permalink