git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] block-sha1: Use mozilla-sha1 copyright and license information

From
USUlrik Sverdrup <ulrik.sverdrup@gmail.com>
Date
Aug 24, 2009, 13:52 UTC
Message-ID
<a1b6cb1b0908240652s4714eadeha7c7997fec2ab985@mail.gmail.com>
In-Reply-To
<alpine.LFD.2.00.0908240923360.6044@xanadu.home>
2009/8/24 Nicolas Pitre <nico@cam.org>:
Show 22 quoted lines
>
> The Mozilla SHA1 is already removed from the tree in "next", and
> block-sha1/sha1.c header modified accordingly.
>
> As there is nothing remaining from the Mozilla SHA1 code, I don't think
> copying that Mozilla License block verbatim is appropriate.  As Linus
> has put it himself, the Mozilla SHA1 code was more inspirational than
> anything else.
>
> And even if some license claim could be made, the MPL section was
> deleted anyway (as explicitly allowed), meaning that only the GPL (by
> vertu of being included in a GPL project) would then apply.
>
> A question was recently sent to all contributors (see the mail
> archive) to determine if they
> would agree
> to a relicensing of that code to make wider license compatibility.
> George Spelvin even rewrote that code as well with the goal of
> putting his version in the public domain.  No definitive conclusion
> emerged so far though.
>
> Therefore I don't think this patch is appropriate.
Agreed. I just didn't look into next.
Ulrik
Previous: Nicolas Pitre
Message 3 of 3 in “block-sha1: Use mozilla-sha1 copyright and license information”
  1. block-sha1: Use mozilla-sha1 copyright and license informationUlrik Sverdrup, Aug 24, 2009
  2. Nicolas PitreAug 24, 2009
  3. Ulrik SverdrupAug 24, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.