From: Schrober <franzschrober@yahoo.de>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>
Subject: [PATCH 0/2] sparse: Relicense from non-dfsg-free OSL 1.1 to MIT license
Date: Tue, 26 Nov 2013 18:09:19 +0100 [thread overview]
Message-ID: <2707831.Oy8a70NHiK@bentobox> (raw)
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
Hi,
many different people (especially Dan Carpenter) worked quite hard to contact
all people with significant contributions. The two changes are the ones which
should change the license from the problematic OSL[1] to the more liberal MIT
license. The initial agreement was reached when Novafora (successor in
interest to Transmeta Corporation) accepted such a license [2]. The commit
provided by them is attached as "relicense.bundle" and has to be
unbundled+merged in the sparse repository before the following patches can be
applied.
The agreements of each person can be found in the relicense.tar.xz. The
changes can also be pulled from
git pull https://github.com/franzschrober/sparse.git master
Btw. when somebody has to ask me in the future about a license change of these
two patches: do whatever you want. They can be considered public domain.
[1] https://wiki.debian.org/DFSGLicenses#Open_Software_License_.28OSL.29_v1.1
[2] http://lwn.net/Articles/328560/
--
Franz Schrober
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: relicense.bundle --]
[-- Type: text/plain; charset="UTF-8"; name="relicense.bundle", Size: 1757 bytes --]
# v2 git bundle
-1bcc92138dcdf718dc3e0c694565f56e669d6ee3 Do a proper scope allocator, don't use the "bytes" allocator that doesn't have any alignment guarantees.
23525c14bc263d70165fedf469d35cdb31b0ac35 refs/heads/license
PACK\0\0\0\x02\0\0\0\x03\x1cx¥ÁJÅ0\x10E÷ùYê¢%mÚ´\x11\x11ÑÕ\x13\x14÷\x03ÉdÒ\x16_¦JÿÞ,¸\x11\Ípçrfî¤H\x04ë¹ä
©9w¢ªºé{N\x16cÝ9k\x1aì^[¶èH>Ae\x10U]Þ¢u] R5l]+IJe%`zKcð\x12\fÅ\x04wd'\x1cé\x15®£9··>¼i\x17¢.1Ì7PÕBuBɶw³¬ÎSJô\x1f\x06{:Ïá4!ù`:§ØÖÉ\x0fðx8~êåoë
gÈÂLñ´Cx÷dÁìpÌu¦¤á>Ä%ûÓ\x14<lÞæCÓH? \0\x17_Ôe8ê5C¾ \x0fÚo:f¸ü}U^2¶NC^T\x04ç
³_ý9:û\0°\b(û\x0e:ñ\v\x7f÷lܸ\x01Ãê+N ¿î®\fzxÌ>ÝÝÐÀÀÌÄDÁÍ1ÁõÔ·îd\x14¼^®)ÿù¯X+Ó\x02+¨´§³«_°+ƪ¾ðýÿW
ßSþ¥äµÂ¹`%\x13Ý\x19M&f+\x02^% ±A\x15H\S\a\x12ÿÄd5F ôd/F\x05 \r&{\x18ÕäfF âÉ×ÀäOF\r ©Ä\x04b»É\f&Þ L ½[Àä\r0ù ¤RY\x13Hú3+)\x01\x1dXYªÌPÝǸ¹æe_àöS¿Zôajágþ\x18\0\x1eDN\x10ðh¡+\98÷ÑI»·c2peßpxmUMoÛ8\x10=/ÿÃ\x02ÚBóÑx×½)6\x1d³%CÍÆ\x16^[Y4H*FNú\x11ûGö¿õÐk²M\x16\v\b\x16DrÞ{ófþ±ü¹êX¬åZ^[ cmvôvJ7\x01ض(ÐZm@5ô84h\x1d8\r¹Ý¢{\x7fUt`õ\x02µ*°±hA6/@»~Ó^«\x10vFoÜÂÝIcñ,\0 Ý\x18,neãTÁúU\x13\0©}¥ª*ôîŨMå(\x1enmý\x02{i¡Âº\x04â|UÄÞ("\x01å\x11dOÒ|¬ÅÆùl
'Õ°ËUQº«Ëë?Ë¢\ÿqI¯k¼(£Ï7ÃõÍ\x10ÃQ9D¼½r\x15\x01l]EÚÚ\x19r»R:dÝ×¶A¸ú\x1cÀÕÅÅõ)Ýr`p§rÚ¼tV¾\f\x06ô{þ¦Áú\n3ص«-¶\x12±\x1e\x1c¼9¾Î=\x06¥jÐ\x19EÛ%èÍ¥¡¬.{²Q\0mS¢é ׺®õ^5S\x19¾0²ääÞâãAÞ»
þv2ý=úô{Gæ^[DAQI³ÁÀ¼¯%\x1aK®êªñ\x14ùÂ\x1crU\x16¬^»½$£½ï\x1a§PäM ¥.Ú-\x19\x7f(ÊZÕÔ^[\x1fH,;Ë\x11g\x1f{\x12e\r\x1dÇgrÚë×÷Ñ\x03Å¡7USÔmI"Øi»V[u¤ðá}ÂÖ£¶RðB\x03ØêRý^[û¼ÈõZÙ*`¥òЫÖÑbgýjï]à3\x19Pµ-ÖµPøÚÈ'yý\x19¢aä\x0e 8Ô\x13ï+½}
´nMCXö k2Í\x0fÚê;\x16~´«º·E,tSª~¨9AÉ~~;\x0f¦©98Þ× Wawá¸e+IâWx´\fKF\x06Ë7ù\x18ÏO½LóGöïºÿLìIü9 qÈiþ\x10¦\x1cD\x064¹\x17\x13>³0£o\x1aæ\aÏe\x0et"\rãü\x11)ñ#|\x13ñ$\0þ×"åYÆ\x14Ä|\x11 Nk"\x1eGËïàââ$ï \x12s\x13jg<b \x11\x1aót<£ÏðVD"\x7f\f`*ò@aJ¨!,Â4\x17ãe\x14¦°X¦$ãÄ?!ÜXÄÓhøÇù9\x131\x01¿§\x0fÈfa\x14õTá2uIJD)Åc*îf9ÌhÂiñ´ð6â\a®ø£PÌ\x03óð÷Q Á¤ý±£¼\x19ï0¤g$ö®8Oé3`y毡\x0f¢Ëx\0a*2ïÉ4M\bß;J!IB1?Àx·½nöZ\x14:âóXfü_1\x13\x1eFùà·\x15¤²T¯Ð8¸ÅnI|b÷ªø° QS¥¿*©\ax³Q\r¢ñ³ö\x7fÿ\x13,£[ñ«öÓ2\x0eY¸3ªËÃ58b¦ÕÔ«ª¡æò³\x7fìnßÐÿüøô\vÞª%ùcÿ\x15ûþ³+éá³XKÄ¥©Kرù
[-- Attachment #3: relicense.tar.xz --]
[-- Type: application/x-xz-compressed-tar, Size: 43284 bytes --]
next reply other threads:[~2013-11-26 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 17:09 Schrober [this message]
2013-11-26 17:11 ` [PATCH 1/2] sparse: Relicense under the MIT license Franz Schrober
2013-11-26 17:11 ` [PATCH 2/2] FAQ: Remove outdated section about the license Franz Schrober
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2707831.Oy8a70NHiK@bentobox \
--to=franzschrober@yahoo.de \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).