Fossil

Check-in [7cfe191b]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Grammar fix to previous
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | bsd-vs-gpl
Files: files | file ages | folders
SHA3-256: 7cfe191bf15f37783bd557520522139d63ab0be462f80ada90a6d786cc592272
User & Date: wyoung 2019-07-12 05:03:35
Context
2019-07-12
13:25
Merged in Linux vs SQLite stuff from trunk check-in: f5321731 user: wyoung tags: bsd-vs-gpl
05:03
Grammar fix to previous check-in: 7cfe191b user: wyoung tags: bsd-vs-gpl
04:57
Rewrote the "GPL vs. BSD" section in www/fossil-v-git.wiki. See forum post here for justification and discussion: https://fossil-scm.org/forum/forumpost/3239c30fff check-in: 68a7563e user: wyoung tags: bsd-vs-gpl
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/fossil-v-git.wiki.

271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
<h3>2.9 GPL vs. BSD</h3>

Git is covered by the GPL license, whereas Fossil is covered by
[https://fossil-scm.org/fossil/file/COPYRIGHT-BSD2.txt|a two-clause BSD
style license].

The key emphasis in the GPL is that if you distribute a binary built from
a version of a piece of GPL-licensed source code that you changed, you
must also distribute the source code used to produce that binary. To
enforce that, the GPL licenses have their famous
[https://en.wikipedia.org/wiki/Viral_license|viral provisions].

We can summarize the key emphasis of the BSD style licenses as "Please
don't sue us." A BSD style license places very little restriction on
what you are allowed to do with the source code or the binaries produced







|







271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
<h3>2.9 GPL vs. BSD</h3>

Git is covered by the GPL license, whereas Fossil is covered by
[https://fossil-scm.org/fossil/file/COPYRIGHT-BSD2.txt|a two-clause BSD
style license].

The key emphasis in the GPL is that if you distribute a binary built from
a piece of GPL-licensed source code that you changed, you
must also distribute the source code used to produce that binary. To
enforce that, the GPL licenses have their famous
[https://en.wikipedia.org/wiki/Viral_license|viral provisions].

We can summarize the key emphasis of the BSD style licenses as "Please
don't sue us." A BSD style license places very little restriction on
what you are allowed to do with the source code or the binaries produced