Fossil SCM

Moved the comment about learning from Git's design mistakes to a place higher up in the document where it makes more sense. It was almost a non sequitur where it was before.

wyoung 2019-08-08 05:55 trunk
Commit 0e0d76ee274e1591ab1fcd18fbd03075f5696db1f010fd500a9e3158d8f275c4
1 file changed +4 -3
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -203,10 +203,13 @@
203203
Fossil simply calls "prev", but there <i>is</i> a "next"
204204
[./checkin_names.wiki|special check-in name] in Fossil. It is why Fossil
205205
has so many [./webpage-ex.md|built-in status reports] to help maintain
206206
situational awareness, aid comprehension, and avoid errors.
207207
208
+These differences are due, in part, to Fossil's start a year later than
209
+Git: we were able to learn from its key design mistakes.
210
+
208211
209212
<h3 id="portable">2.4 Portable</h3>
210213
211214
Fossil is largely written in ISO C, almost purely conforming to the
212215
original 1989 standard. We make very little use of
@@ -409,13 +412,11 @@
409412
having such a large set of developers working on such a large code base.
410413
411414
95% of the code in SQLite comes from just four programmers, and 64% of
412415
it is from the lead developer alone. The SQLite developers know each
413416
other well and interact daily. Fossil was designed for this development
414
-model. As well, we think the fact of Fossil's birth a year later
415
-than Git allowed it to learn from some of the key design mistakes in
416
-Git.
417
+model.
417418
418419
We think you should ask yourself whether you have Linus Torvalds scale
419420
software configuration management problems or D. Richard Hipp scale
420421
problems when choosing your DVCS. An
421422
[https://en.wikipedia.org/wiki/Impact_wrench|automotive air impact
422423
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -203,10 +203,13 @@
203 Fossil simply calls "prev", but there <i>is</i> a "next"
204 [./checkin_names.wiki|special check-in name] in Fossil. It is why Fossil
205 has so many [./webpage-ex.md|built-in status reports] to help maintain
206 situational awareness, aid comprehension, and avoid errors.
207
 
 
 
208
209 <h3 id="portable">2.4 Portable</h3>
210
211 Fossil is largely written in ISO C, almost purely conforming to the
212 original 1989 standard. We make very little use of
@@ -409,13 +412,11 @@
409 having such a large set of developers working on such a large code base.
410
411 95% of the code in SQLite comes from just four programmers, and 64% of
412 it is from the lead developer alone. The SQLite developers know each
413 other well and interact daily. Fossil was designed for this development
414 model. As well, we think the fact of Fossil's birth a year later
415 than Git allowed it to learn from some of the key design mistakes in
416 Git.
417
418 We think you should ask yourself whether you have Linus Torvalds scale
419 software configuration management problems or D. Richard Hipp scale
420 problems when choosing your DVCS. An
421 [https://en.wikipedia.org/wiki/Impact_wrench|automotive air impact
422
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -203,10 +203,13 @@
203 Fossil simply calls "prev", but there <i>is</i> a "next"
204 [./checkin_names.wiki|special check-in name] in Fossil. It is why Fossil
205 has so many [./webpage-ex.md|built-in status reports] to help maintain
206 situational awareness, aid comprehension, and avoid errors.
207
208 These differences are due, in part, to Fossil's start a year later than
209 Git: we were able to learn from its key design mistakes.
210
211
212 <h3 id="portable">2.4 Portable</h3>
213
214 Fossil is largely written in ISO C, almost purely conforming to the
215 original 1989 standard. We make very little use of
@@ -409,13 +412,11 @@
412 having such a large set of developers working on such a large code base.
413
414 95% of the code in SQLite comes from just four programmers, and 64% of
415 it is from the lead developer alone. The SQLite developers know each
416 other well and interact daily. Fossil was designed for this development
417 model.
 
 
418
419 We think you should ask yourself whether you have Linus Torvalds scale
420 software configuration management problems or D. Richard Hipp scale
421 problems when choosing your DVCS. An
422 [https://en.wikipedia.org/wiki/Impact_wrench|automotive air impact
423

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button