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

Overview
Comment:Fix minor typo in the fossil-v-git document.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:2e8f2887110925c06aec1cc7712fb98eff1163c33f9efb114033c1abfd7eaf71
User & Date: drh 2018-04-21 22:58:56
Context
2018-04-25
13:34
Update the built-in SQLite to the latest 3.24.0 alpha version. check-in: de76c92a user: drh tags: trunk
2018-04-21
22:58
Fix minor typo in the fossil-v-git document. check-in: 2e8f2887 user: drh tags: trunk
2018-04-11
20:34
Correct minor typo check-in: 805a58c3 user: andygoth tags: trunk
Changes

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

214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
<h3>3.8 GPL vs. BSD</h3>

Git is covered by the GPL license whereas Fossil is covered by
a two-clause BSD license.

Consider the difference between GPL and BSD licenses:  GPL is designed
to make writing easier at the expense of making reading harder.  BSD is
designed to make reading easier and the expense of making writing harder.

To a first approximation, the GPL license grants the right to read
source code to anyone who promises to give back enhancements.  In other
words, the act of reading GPL source code (a prerequiste for making changes)
implies acceptance of the license which requires updates to be contributed
back under the same license.  (The details are more complex, but the
foregoing captures the essence of the idea.)  A big advantage of the GPL







|







214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
<h3>3.8 GPL vs. BSD</h3>

Git is covered by the GPL license whereas Fossil is covered by
a two-clause BSD license.

Consider the difference between GPL and BSD licenses:  GPL is designed
to make writing easier at the expense of making reading harder.  BSD is
designed to make reading easier at the expense of making writing harder.

To a first approximation, the GPL license grants the right to read
source code to anyone who promises to give back enhancements.  In other
words, the act of reading GPL source code (a prerequiste for making changes)
implies acceptance of the license which requires updates to be contributed
back under the same license.  (The details are more complex, but the
foregoing captures the essence of the idea.)  A big advantage of the GPL