Fossil SCM
Added footnote 2 to the fossil-v-git doc, which explains that not "everything" on fossil-scm.org is in the main Fossil self-hosting repo, and links to info explaining the details.
Commit
d23a8453c55bcfbaee76660a7d6385dc5c6b78def376242660194a6b6119960b
Parent
0ef227b77cfc205…
1 file changed
+20
-8
+20
-8
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -59,25 +59,29 @@ | ||
| 59 | 59 | These additional capabilities are available for Git as 3rd-party |
| 60 | 60 | add-ons, but with Fossil they are integrated into |
| 61 | 61 | the design. One way to describe Fossil is that it is |
| 62 | 62 | "[https://github.com/ | GitHub]-in-a-box." |
| 63 | 63 | |
| 64 | -If you clone [https://github.com/git/git|Git's self-hosting repository], | |
| 65 | -you get just Git's source code. | |
| 66 | -If you clone Fossil's self-hosting repository, you get the entire | |
| 67 | -Fossil website — source code, documentation, ticket history, and so forth. | |
| 68 | -That means you get a copy of this very article and all of its historical | |
| 69 | -versions, plus the same for all of the other public content on this site. | |
| 70 | - | |
| 71 | 64 | For developers who choose to self-host projects (rather than using a |
| 72 | 65 | 3rd-party service such as GitHub) Fossil is much easier to set up, since |
| 73 | 66 | the stand-alone Fossil executable together with a [./server.wiki#cgi|2-line CGI script] |
| 74 | 67 | suffice to instantiate a full-featured developer website. To accomplish |
| 75 | 68 | the same using Git requires locating, installing, configuring, integrating, |
| 76 | 69 | and managing a wide assortment of separate tools. Standing up a developer |
| 77 | 70 | website using Fossil can be done in minutes, whereas doing the same using |
| 78 | 71 | Git requires hours or days. |
| 72 | + | |
| 73 | +All of this is complete and self-contained in Fossil. | |
| 74 | +If you clone [https://github.com/git/git|Git's self-hosting repository], | |
| 75 | +you get just Git's source code. | |
| 76 | +If you clone Fossil's self-hosting repository, you get the entire | |
| 77 | +Fossil website — source code, documentation, ticket history, and so forth. | |
| 78 | +That means you get a copy of this very article and all of its historical | |
| 79 | +versions, plus the same for all of the other public content on this | |
| 80 | +site.² | |
| 81 | + | |
| 82 | + | |
| 79 | 83 | |
| 80 | 84 | <h3 id="database">2.2 Database</h3> |
| 81 | 85 | |
| 82 | 86 | The baseline data structures for Fossil and Git are the same, modulo |
| 83 | 87 | formatting details. Both systems store check-ins as immutable |
| @@ -197,11 +201,11 @@ | ||
| 197 | 201 | [https://www.git-scm.com/docs/git-request-pull|pull requests] offer |
| 198 | 202 | a low-friction path to accepting |
| 199 | 203 | [https://www.jonobacon.com/2012/07/25/building-strong-community-structural-integrity/|drive-by |
| 200 | 204 | contributions]. Fossil's closest equivalent is its unique |
| 201 | 205 | [/help?cmd=bundle|bundle] feature, which requires higher engagement |
| 202 | - than firing off a PR.² This difference comes directly from the | |
| 206 | + than firing off a PR.³ This difference comes directly from the | |
| 203 | 207 | initial designed purpose for each tool: the SQLite project doesn't |
| 204 | 208 | accept outside contributions from previously-unknown developers, but |
| 205 | 209 | the Linux kernel does.</p></li> |
| 206 | 210 | |
| 207 | 211 | <li><p><b>No rebasing:</b> When your local repo clone syncs changes |
| @@ -589,10 +593,18 @@ | ||
| 589 | 593 | missing features to stock |
| 590 | 594 | Git, but because they're not part of Git proper, |
| 591 | 595 | [./mirrortogithub.md|exporting a Fossil repository to GitHub] will |
| 592 | 596 | still not include them; Fossil tickets do not become GitHub issues, |
| 593 | 597 | for example. |
| 598 | + | |
| 599 | + <li><p>The <tt>fossil-scm.org</tt> web site is actually hosted in | |
| 600 | + several parts, so that it is not strictly true that "everything" on | |
| 601 | + it is in the self-hosting Fossil project repo. The web forum is | |
| 602 | + hosted as a separate Fossil repo from the code for administration | |
| 603 | + reasons, and the Download page content isn't normally sync'd with a | |
| 604 | + "<tt>fossil clone</tt>" command due to [./aboutdownload.wiki|the way | |
| 605 | + it's implemented]. | |
| 594 | 606 | |
| 595 | 607 | <li><p>Both Fossil and Git support |
| 596 | 608 | [https://en.wikipedia.org/wiki/Patch_(Unix)|<tt>patch(1)</tt> |
| 597 | 609 | files], a common way to allow drive-by contributions, but it's a |
| 598 | 610 | lossy contribution path for both systems. Unlike Git PRs and Fossil |
| 599 | 611 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -59,25 +59,29 @@ | |
| 59 | These additional capabilities are available for Git as 3rd-party |
| 60 | add-ons, but with Fossil they are integrated into |
| 61 | the design. One way to describe Fossil is that it is |
| 62 | "[https://github.com/ | GitHub]-in-a-box." |
| 63 | |
| 64 | If you clone [https://github.com/git/git|Git's self-hosting repository], |
| 65 | you get just Git's source code. |
| 66 | If you clone Fossil's self-hosting repository, you get the entire |
| 67 | Fossil website — source code, documentation, ticket history, and so forth. |
| 68 | That means you get a copy of this very article and all of its historical |
| 69 | versions, plus the same for all of the other public content on this site. |
| 70 | |
| 71 | For developers who choose to self-host projects (rather than using a |
| 72 | 3rd-party service such as GitHub) Fossil is much easier to set up, since |
| 73 | the stand-alone Fossil executable together with a [./server.wiki#cgi|2-line CGI script] |
| 74 | suffice to instantiate a full-featured developer website. To accomplish |
| 75 | the same using Git requires locating, installing, configuring, integrating, |
| 76 | and managing a wide assortment of separate tools. Standing up a developer |
| 77 | website using Fossil can be done in minutes, whereas doing the same using |
| 78 | Git requires hours or days. |
| 79 | |
| 80 | <h3 id="database">2.2 Database</h3> |
| 81 | |
| 82 | The baseline data structures for Fossil and Git are the same, modulo |
| 83 | formatting details. Both systems store check-ins as immutable |
| @@ -197,11 +201,11 @@ | |
| 197 | [https://www.git-scm.com/docs/git-request-pull|pull requests] offer |
| 198 | a low-friction path to accepting |
| 199 | [https://www.jonobacon.com/2012/07/25/building-strong-community-structural-integrity/|drive-by |
| 200 | contributions]. Fossil's closest equivalent is its unique |
| 201 | [/help?cmd=bundle|bundle] feature, which requires higher engagement |
| 202 | than firing off a PR.² This difference comes directly from the |
| 203 | initial designed purpose for each tool: the SQLite project doesn't |
| 204 | accept outside contributions from previously-unknown developers, but |
| 205 | the Linux kernel does.</p></li> |
| 206 | |
| 207 | <li><p><b>No rebasing:</b> When your local repo clone syncs changes |
| @@ -589,10 +593,18 @@ | |
| 589 | missing features to stock |
| 590 | Git, but because they're not part of Git proper, |
| 591 | [./mirrortogithub.md|exporting a Fossil repository to GitHub] will |
| 592 | still not include them; Fossil tickets do not become GitHub issues, |
| 593 | for example. |
| 594 | |
| 595 | <li><p>Both Fossil and Git support |
| 596 | [https://en.wikipedia.org/wiki/Patch_(Unix)|<tt>patch(1)</tt> |
| 597 | files], a common way to allow drive-by contributions, but it's a |
| 598 | lossy contribution path for both systems. Unlike Git PRs and Fossil |
| 599 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -59,25 +59,29 @@ | |
| 59 | These additional capabilities are available for Git as 3rd-party |
| 60 | add-ons, but with Fossil they are integrated into |
| 61 | the design. One way to describe Fossil is that it is |
| 62 | "[https://github.com/ | GitHub]-in-a-box." |
| 63 | |
| 64 | For developers who choose to self-host projects (rather than using a |
| 65 | 3rd-party service such as GitHub) Fossil is much easier to set up, since |
| 66 | the stand-alone Fossil executable together with a [./server.wiki#cgi|2-line CGI script] |
| 67 | suffice to instantiate a full-featured developer website. To accomplish |
| 68 | the same using Git requires locating, installing, configuring, integrating, |
| 69 | and managing a wide assortment of separate tools. Standing up a developer |
| 70 | website using Fossil can be done in minutes, whereas doing the same using |
| 71 | Git requires hours or days. |
| 72 | |
| 73 | All of this is complete and self-contained in Fossil. |
| 74 | If you clone [https://github.com/git/git|Git's self-hosting repository], |
| 75 | you get just Git's source code. |
| 76 | If you clone Fossil's self-hosting repository, you get the entire |
| 77 | Fossil website — source code, documentation, ticket history, and so forth. |
| 78 | That means you get a copy of this very article and all of its historical |
| 79 | versions, plus the same for all of the other public content on this |
| 80 | site.² |
| 81 | |
| 82 | |
| 83 | |
| 84 | <h3 id="database">2.2 Database</h3> |
| 85 | |
| 86 | The baseline data structures for Fossil and Git are the same, modulo |
| 87 | formatting details. Both systems store check-ins as immutable |
| @@ -197,11 +201,11 @@ | |
| 201 | [https://www.git-scm.com/docs/git-request-pull|pull requests] offer |
| 202 | a low-friction path to accepting |
| 203 | [https://www.jonobacon.com/2012/07/25/building-strong-community-structural-integrity/|drive-by |
| 204 | contributions]. Fossil's closest equivalent is its unique |
| 205 | [/help?cmd=bundle|bundle] feature, which requires higher engagement |
| 206 | than firing off a PR.³ This difference comes directly from the |
| 207 | initial designed purpose for each tool: the SQLite project doesn't |
| 208 | accept outside contributions from previously-unknown developers, but |
| 209 | the Linux kernel does.</p></li> |
| 210 | |
| 211 | <li><p><b>No rebasing:</b> When your local repo clone syncs changes |
| @@ -589,10 +593,18 @@ | |
| 593 | missing features to stock |
| 594 | Git, but because they're not part of Git proper, |
| 595 | [./mirrortogithub.md|exporting a Fossil repository to GitHub] will |
| 596 | still not include them; Fossil tickets do not become GitHub issues, |
| 597 | for example. |
| 598 | |
| 599 | <li><p>The <tt>fossil-scm.org</tt> web site is actually hosted in |
| 600 | several parts, so that it is not strictly true that "everything" on |
| 601 | it is in the self-hosting Fossil project repo. The web forum is |
| 602 | hosted as a separate Fossil repo from the code for administration |
| 603 | reasons, and the Download page content isn't normally sync'd with a |
| 604 | "<tt>fossil clone</tt>" command due to [./aboutdownload.wiki|the way |
| 605 | it's implemented]. |
| 606 | |
| 607 | <li><p>Both Fossil and Git support |
| 608 | [https://en.wikipedia.org/wiki/Patch_(Unix)|<tt>patch(1)</tt> |
| 609 | files], a common way to allow drive-by contributions, but it's a |
| 610 | lossy contribution path for both systems. Unlike Git PRs and Fossil |
| 611 |