Fossil SCM

Record Olorin's disputes with the fossil-v-git document. Also fix a stale table-of-contents link in that same document.

drh 2024-09-18 11:42 trunk
Commit b08f062316aa5517f905e18fde19291c47de15c8751f28b4aab1e745710be0fc
1 file changed +6 -6
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -70,18 +70,13 @@
7070
<td>Designed for Linux kernel development</td>
7171
<td>Designed for SQLite development</td>
7272
<td><a href="#scale">2.5.2&nbsp;&darr;</a></td>
7373
</tr>
7474
<tr>
75
- <td>Many contributors</td>
76
- <td>Select contributors</td>
77
- <td><a href="#contrib">2.5.3&nbsp;&darr;</a></td>
78
-</tr>
79
-<tr>
8075
<td>Focus on individual branches</td>
8176
<td>Focus on the entire tree of changes</td>
82
- <td><a href="#branches">2.5.4&nbsp;&darr;</a></td>
77
+ <td><a href="#branches">2.5.3&nbsp;&darr;</a></td>
8378
</tr>
8479
<tr>
8580
<td>One check-out per repository</td>
8681
<td>Many check-outs per repository</td>
8782
<td><a href="#checkouts">2.6&nbsp;&darr;</a></td>
@@ -591,10 +586,13 @@
591586
and its handful of active committers. Seeing all
592587
changes on all branches all at once helps keep the whole team
593588
up-to-date with what everybody else is doing, resulting in a more
594589
tightly focused and cohesive implementation.
595590
591
+Parts of this section are [https://fossil-scm.org/forum/forumpost/5961e969fa|disputed]
592
+by [https://github.com/olorin37|Jakub A. G.].
593
+
596594
597595
<h3 id="checkouts">2.6 One vs. Many Check-outs per Repository</h3>
598596
599597
Because Git commingles the repository data with the initial checkout of
600598
that repository, the default mode of operation in Git is to stick to that
@@ -660,10 +658,12 @@
660658
661659
Plus,
662660
<tt>cd</tt> is faster to type than <tt>git checkout</tt> or <tt>fossil
663661
update</tt>.
664662
663
+Parts of this section are [https://fossil-scm.org/forum/forumpost/5961e969fa|disputed]
664
+by [https://github.com/olorin37|Jakub A. G.].
665665
666666
<h3 id="history">2.7 What you should have done vs. What you actually did</h3>
667667
668668
Git puts a lot of emphasis on maintaining
669669
a "clean" check-in history. Extraneous and experimental branches by
670670
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -70,18 +70,13 @@
70 <td>Designed for Linux kernel development</td>
71 <td>Designed for SQLite development</td>
72 <td><a href="#scale">2.5.2&nbsp;&darr;</a></td>
73 </tr>
74 <tr>
75 <td>Many contributors</td>
76 <td>Select contributors</td>
77 <td><a href="#contrib">2.5.3&nbsp;&darr;</a></td>
78 </tr>
79 <tr>
80 <td>Focus on individual branches</td>
81 <td>Focus on the entire tree of changes</td>
82 <td><a href="#branches">2.5.4&nbsp;&darr;</a></td>
83 </tr>
84 <tr>
85 <td>One check-out per repository</td>
86 <td>Many check-outs per repository</td>
87 <td><a href="#checkouts">2.6&nbsp;&darr;</a></td>
@@ -591,10 +586,13 @@
591 and its handful of active committers. Seeing all
592 changes on all branches all at once helps keep the whole team
593 up-to-date with what everybody else is doing, resulting in a more
594 tightly focused and cohesive implementation.
595
 
 
 
596
597 <h3 id="checkouts">2.6 One vs. Many Check-outs per Repository</h3>
598
599 Because Git commingles the repository data with the initial checkout of
600 that repository, the default mode of operation in Git is to stick to that
@@ -660,10 +658,12 @@
660
661 Plus,
662 <tt>cd</tt> is faster to type than <tt>git checkout</tt> or <tt>fossil
663 update</tt>.
664
 
 
665
666 <h3 id="history">2.7 What you should have done vs. What you actually did</h3>
667
668 Git puts a lot of emphasis on maintaining
669 a "clean" check-in history. Extraneous and experimental branches by
670
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -70,18 +70,13 @@
70 <td>Designed for Linux kernel development</td>
71 <td>Designed for SQLite development</td>
72 <td><a href="#scale">2.5.2&nbsp;&darr;</a></td>
73 </tr>
74 <tr>
 
 
 
 
 
75 <td>Focus on individual branches</td>
76 <td>Focus on the entire tree of changes</td>
77 <td><a href="#branches">2.5.3&nbsp;&darr;</a></td>
78 </tr>
79 <tr>
80 <td>One check-out per repository</td>
81 <td>Many check-outs per repository</td>
82 <td><a href="#checkouts">2.6&nbsp;&darr;</a></td>
@@ -591,10 +586,13 @@
586 and its handful of active committers. Seeing all
587 changes on all branches all at once helps keep the whole team
588 up-to-date with what everybody else is doing, resulting in a more
589 tightly focused and cohesive implementation.
590
591 Parts of this section are [https://fossil-scm.org/forum/forumpost/5961e969fa|disputed]
592 by [https://github.com/olorin37|Jakub A. G.].
593
594
595 <h3 id="checkouts">2.6 One vs. Many Check-outs per Repository</h3>
596
597 Because Git commingles the repository data with the initial checkout of
598 that repository, the default mode of operation in Git is to stick to that
@@ -660,10 +658,12 @@
658
659 Plus,
660 <tt>cd</tt> is faster to type than <tt>git checkout</tt> or <tt>fossil
661 update</tt>.
662
663 Parts of this section are [https://fossil-scm.org/forum/forumpost/5961e969fa|disputed]
664 by [https://github.com/olorin37|Jakub A. G.].
665
666 <h3 id="history">2.7 What you should have done vs. What you actually did</h3>
667
668 Git puts a lot of emphasis on maintaining
669 a "clean" check-in history. Extraneous and experimental branches by
670

Keyboard Shortcuts

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