Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
|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|
|User & Date:||drh 2018-04-21 22:58:56|
|13:34||Update the built-in SQLite to the latest 3.24.0 alpha version. check-in: de76c92a user: drh tags: trunk|
|22:58||Fix minor typo in the fossil-v-git document. check-in: 2e8f2887 user: drh tags: trunk|
|20:34||Correct minor typo check-in: 805a58c3 user: andygoth tags: trunk|
Changes to www/fossil-v-git.wiki.
214 214 <h3>3.8 GPL vs. BSD</h3> 215 215 216 216 Git is covered by the GPL license whereas Fossil is covered by 217 217 a two-clause BSD license. 218 218 219 219 Consider the difference between GPL and BSD licenses: GPL is designed 220 220 to make writing easier at the expense of making reading harder. BSD is 221 -designed to make reading easier and the expense of making writing harder. 221 +designed to make reading easier at the expense of making writing harder. 222 222 223 223 To a first approximation, the GPL license grants the right to read 224 224 source code to anyone who promises to give back enhancements. In other 225 225 words, the act of reading GPL source code (a prerequiste for making changes) 226 226 implies acceptance of the license which requires updates to be contributed 227 227 back under the same license. (The details are more complex, but the 228 228 foregoing captures the essence of the idea.) A big advantage of the GPL