Fossil SCM
Moved numbered digressions in fossil-v-git down to the end of the document as a new "Asides and Digressions" section. These are things we don't want cluttering the main argument, not merely big parentheticals.
Commit
845262742eaaeddb6de552db585c59d79846d17cb0e709cae1bec54eac7afff4
Parent
69e64183f1d92ea…
1 file changed
+23
-15
+23
-15
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -13,16 +13,10 @@ | ||
| 13 | 13 | Keep in mind that you are reading this on a Fossil website, and though |
| 14 | 14 | we try to be fair, the information here |
| 15 | 15 | might be biased in favor of Fossil. Ask around for second opinions from |
| 16 | 16 | people who have used <em>both</em> Fossil and Git. |
| 17 | 17 | |
| 18 | -¹ <small><i>Git does not include a | |
| 19 | -wiki, a ticket tracker, a forum, or a tech-note feature, so those elements will not transfer when | |
| 20 | -exporting from Fossil to Git. GitHub adds some of these to stock Git, | |
| 21 | -but because they're not part of Git proper, [./mirrortogithub.md|exporting a Fossil | |
| 22 | -repository to GitHub] will still not include them; Fossil tickets do not | |
| 23 | -become GitHub issues, for example.</i></small> | |
| 24 | 18 | |
| 25 | 19 | <h2>2.0 Differences Between Fossil And Git</h2> |
| 26 | 20 | |
| 27 | 21 | Differences between Fossil and Git are summarized by the following table, |
| 28 | 22 | with further description in the text that follows. |
| @@ -252,19 +246,10 @@ | ||
| 252 | 246 | awareness. |
| 253 | 247 | |
| 254 | 248 | Each DVCS can be used in the opposite style, but doing so works against |
| 255 | 249 | their low-friction paths. |
| 256 | 250 | |
| 257 | -² <small><i>Both Fossil and Git support | |
| 258 | -[https://en.wikipedia.org/wiki/Patch_(Unix)|<tt>patch(1)</tt> files], | |
| 259 | -which is a common way to allow drive-by contributions, but it's a lossy | |
| 260 | -contribution path for both systems. Unlike Git PRs and Fossil bundles, | |
| 261 | -patches collapse mulitple checkins together, they don't include check-in | |
| 262 | -comments, and the cannot encode changes made above the individual file | |
| 263 | -content layer: branching decisisions, tag changes, file renames, file | |
| 264 | -deletions, etc.</small> | |
| 265 | - | |
| 266 | 251 | |
| 267 | 252 | <h4 id="scale">2.3.2 Scale</h4> |
| 268 | 253 | |
| 269 | 254 | The Linux kernel has a far bigger developer community than that of |
| 270 | 255 | SQLite: there are thousands and thousands of contributors to Linux, most |
| @@ -528,5 +513,28 @@ | ||
| 528 | 513 | The [/help?cmd=push|fossil push], [/help?cmd=pull|fossil pull], and |
| 529 | 514 | [/help?cmd=sync|fossil sync] commands do not provide the capability to |
| 530 | 515 | push or pull individual branches. Pushing and pulling in Fossil is |
| 531 | 516 | all or nothing. This is in keeping with Fossil's emphasis on maintaining |
| 532 | 517 | a complete record and on sharing everything between all developers. |
| 518 | + | |
| 519 | +<hr/> | |
| 520 | + | |
| 521 | +<h3>Asides and Digressions</h3> | |
| 522 | + | |
| 523 | +<i><small><ol> | |
| 524 | + <li><p>Git does not include a wiki, a ticket tracker, a forum, or a | |
| 525 | + tech-note feature, so those elements will not transfer when | |
| 526 | + exporting from Fossil to Git. GitHub adds some of these to stock | |
| 527 | + Git, but because they're not part of Git proper, | |
| 528 | + [./mirrortogithub.md|exporting a Fossil repository to GitHub] will | |
| 529 | + still not include them; Fossil tickets do not become GitHub issues, | |
| 530 | + for example.</p></li> | |
| 531 | + | |
| 532 | + <li><p>Both Fossil and Git support | |
| 533 | + [https://en.wikipedia.org/wiki/Patch_(Unix)|<tt>patch(1)</tt> | |
| 534 | + files], a common way to allow drive-by contributions, but it's a | |
| 535 | + lossy contribution path for both systems. Unlike Git PRs and Fossil | |
| 536 | + bundles, patch files collapse mulitple checkins together, they don't | |
| 537 | + include check-in comments, and they cannot encode changes made above | |
| 538 | + the individual file content layer: you lose branching decisisions, | |
| 539 | + tag changes, file renames, and more when using patch files.</p></li> | |
| 540 | +</ol></i></small> | |
| 533 | 541 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -13,16 +13,10 @@ | |
| 13 | Keep in mind that you are reading this on a Fossil website, and though |
| 14 | we try to be fair, the information here |
| 15 | might be biased in favor of Fossil. Ask around for second opinions from |
| 16 | people who have used <em>both</em> Fossil and Git. |
| 17 | |
| 18 | ¹ <small><i>Git does not include a |
| 19 | wiki, a ticket tracker, a forum, or a tech-note feature, so those elements will not transfer when |
| 20 | exporting from Fossil to Git. GitHub adds some of these to stock Git, |
| 21 | but because they're not part of Git proper, [./mirrortogithub.md|exporting a Fossil |
| 22 | repository to GitHub] will still not include them; Fossil tickets do not |
| 23 | become GitHub issues, for example.</i></small> |
| 24 | |
| 25 | <h2>2.0 Differences Between Fossil And Git</h2> |
| 26 | |
| 27 | Differences between Fossil and Git are summarized by the following table, |
| 28 | with further description in the text that follows. |
| @@ -252,19 +246,10 @@ | |
| 252 | awareness. |
| 253 | |
| 254 | Each DVCS can be used in the opposite style, but doing so works against |
| 255 | their low-friction paths. |
| 256 | |
| 257 | ² <small><i>Both Fossil and Git support |
| 258 | [https://en.wikipedia.org/wiki/Patch_(Unix)|<tt>patch(1)</tt> files], |
| 259 | which is a common way to allow drive-by contributions, but it's a lossy |
| 260 | contribution path for both systems. Unlike Git PRs and Fossil bundles, |
| 261 | patches collapse mulitple checkins together, they don't include check-in |
| 262 | comments, and the cannot encode changes made above the individual file |
| 263 | content layer: branching decisisions, tag changes, file renames, file |
| 264 | deletions, etc.</small> |
| 265 | |
| 266 | |
| 267 | <h4 id="scale">2.3.2 Scale</h4> |
| 268 | |
| 269 | The Linux kernel has a far bigger developer community than that of |
| 270 | SQLite: there are thousands and thousands of contributors to Linux, most |
| @@ -528,5 +513,28 @@ | |
| 528 | The [/help?cmd=push|fossil push], [/help?cmd=pull|fossil pull], and |
| 529 | [/help?cmd=sync|fossil sync] commands do not provide the capability to |
| 530 | push or pull individual branches. Pushing and pulling in Fossil is |
| 531 | all or nothing. This is in keeping with Fossil's emphasis on maintaining |
| 532 | a complete record and on sharing everything between all developers. |
| 533 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -13,16 +13,10 @@ | |
| 13 | Keep in mind that you are reading this on a Fossil website, and though |
| 14 | we try to be fair, the information here |
| 15 | might be biased in favor of Fossil. Ask around for second opinions from |
| 16 | people who have used <em>both</em> Fossil and Git. |
| 17 | |
| 18 | |
| 19 | <h2>2.0 Differences Between Fossil And Git</h2> |
| 20 | |
| 21 | Differences between Fossil and Git are summarized by the following table, |
| 22 | with further description in the text that follows. |
| @@ -252,19 +246,10 @@ | |
| 246 | awareness. |
| 247 | |
| 248 | Each DVCS can be used in the opposite style, but doing so works against |
| 249 | their low-friction paths. |
| 250 | |
| 251 | |
| 252 | <h4 id="scale">2.3.2 Scale</h4> |
| 253 | |
| 254 | The Linux kernel has a far bigger developer community than that of |
| 255 | SQLite: there are thousands and thousands of contributors to Linux, most |
| @@ -528,5 +513,28 @@ | |
| 513 | The [/help?cmd=push|fossil push], [/help?cmd=pull|fossil pull], and |
| 514 | [/help?cmd=sync|fossil sync] commands do not provide the capability to |
| 515 | push or pull individual branches. Pushing and pulling in Fossil is |
| 516 | all or nothing. This is in keeping with Fossil's emphasis on maintaining |
| 517 | a complete record and on sharing everything between all developers. |
| 518 | |
| 519 | <hr/> |
| 520 | |
| 521 | <h3>Asides and Digressions</h3> |
| 522 | |
| 523 | <i><small><ol> |
| 524 | <li><p>Git does not include a wiki, a ticket tracker, a forum, or a |
| 525 | tech-note feature, so those elements will not transfer when |
| 526 | exporting from Fossil to Git. GitHub adds some of these to stock |
| 527 | Git, but because they're not part of Git proper, |
| 528 | [./mirrortogithub.md|exporting a Fossil repository to GitHub] will |
| 529 | still not include them; Fossil tickets do not become GitHub issues, |
| 530 | for example.</p></li> |
| 531 | |
| 532 | <li><p>Both Fossil and Git support |
| 533 | [https://en.wikipedia.org/wiki/Patch_(Unix)|<tt>patch(1)</tt> |
| 534 | files], a common way to allow drive-by contributions, but it's a |
| 535 | lossy contribution path for both systems. Unlike Git PRs and Fossil |
| 536 | bundles, patch files collapse mulitple checkins together, they don't |
| 537 | include check-in comments, and they cannot encode changes made above |
| 538 | the individual file content layer: you lose branching decisisions, |
| 539 | tag changes, file renames, and more when using patch files.</p></li> |
| 540 | </ol></i></small> |
| 541 |