Fossil SCM
Merged two lists of similarities between Fossil and Git into a single instance up at the top of fossil-v-git.wiki.
Commit
3609ff75608d351cb19df0259400af245fbc3eee8b51afb065aaa351a4ff5720
Parent
5e380ec394b5d88…
1 file changed
+25
-18
+25
-18
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -3,14 +3,25 @@ | ||
| 3 | 3 | <h2>1.0 Don't Stress!</h2> |
| 4 | 4 | |
| 5 | 5 | If you start out using one DVCS and later decide you like the other better, |
| 6 | 6 | you can easily [./inout.wiki | move your content].¹ |
| 7 | 7 | |
| 8 | -Fossil and [http://git-scm.com | Git] are very similar in many respects, | |
| 9 | -but they also have important differences. | |
| 10 | -See the table below for | |
| 11 | -a high-level summary and the text that follows for more details. | |
| 8 | +The feature sets of Fossil and [http://git-scm.com | Git] overlap in | |
| 9 | +many ways. Both are | |
| 10 | +[https://en.wikipedia.org/wiki/Distributed_version_control | distributed | |
| 11 | +version control systems] managing a | |
| 12 | +[https://en.wikipedia.org/wiki/Directed_acyclic_graph | directed acyclic | |
| 13 | +graph] (DAG) of [https://en.wikipedia.org/wiki/Merkle_tree | Merkle | |
| 14 | +tree] / [./blockchain.md | block chain] structured check-ins to a local | |
| 15 | +repository clone. In both systems, new content added to the local repo | |
| 16 | +clone can be pushed up to a remote parent, and changes to the remote can | |
| 17 | +be easily pulled down to the local clone. Both systems offer bisecting, | |
| 18 | +private branches, a stash, etc. | |
| 19 | + | |
| 20 | +There are also, however, many important differences between these two | |
| 21 | +DVCSes. We summarize the major differences in the following table, then | |
| 22 | +detail those differences in the following text. | |
| 12 | 23 | |
| 13 | 24 | Keep in mind that you are reading this on a Fossil website, and though |
| 14 | 25 | we try to be fair, the information here |
| 15 | 26 | might be biased in favor of Fossil. Ask around for second opinions from |
| 16 | 27 | people who have used <em>both</em> Fossil and Git. |
| @@ -563,28 +574,24 @@ | ||
| 563 | 574 | for solving the same problem by moving to SHA-256 (a variant of the |
| 564 | 575 | [https://en.wikipedia.org/wiki/SHA-2|older SHA-2 algorithm]) and until |
| 565 | 576 | February 2019 to release a version containing the change. It's looking |
| 566 | 577 | like this will take years more to percolate through the community. |
| 567 | 578 | |
| 568 | -The practical impact of SHAttered on | |
| 569 | -[https://en.wikipedia.org/wiki/Merkle_tree | Merkle tree] / | |
| 570 | -[./blockchain.md | block chain] structred data stores like Git and | |
| 571 | -Fossil isn't clear, but Fossil moved on the problem quickly and had a | |
| 572 | -widely-deployed solution to it years ago. | |
| 579 | +The practical impact of SHAttered on structred data stores like the one | |
| 580 | +in Git and Fossil isn't clear, but you want to have your repositories | |
| 581 | +moved over to a stronger hash algorithm before someone figures out how | |
| 582 | +to make use of the weaknesses in the old one. Fossil's developers moved | |
| 583 | +on this problem quickly and had a widely-deployed solution to it years | |
| 584 | +ago. | |
| 573 | 585 | |
| 574 | 586 | |
| 575 | 587 | <h2 id="missing">3.0 Missing Features</h2> |
| 576 | 588 | |
| 577 | -Most of the capabilities found in Git are also available in Fossil and | |
| 578 | -the other way around. For example, both systems have local check-outs, | |
| 579 | -remote repositories, push/pull/sync, bisect capabilities, and a "stash." | |
| 580 | -Both systems store project history as a directed acyclic graph (DAG) | |
| 581 | -of immutable check-in objects. | |
| 582 | - | |
| 583 | -There are many areas where one system has a feature that is simply | |
| 584 | -missing in the other, however. We covered most of those above, but there | |
| 585 | -are some others we haven't gotten to yet. | |
| 589 | +Although there is a large overlap in capability between Fossil and Git, | |
| 590 | +there are many areas where one system has a feature that is simply | |
| 591 | +missing in the other. We covered most of those above, but there | |
| 592 | +are a few remaining feature differences we haven't gotten to yet. | |
| 586 | 593 | |
| 587 | 594 | |
| 588 | 595 | <h3 id="missing-in-git">3.1 Features found in Fossil but missing from Git</h3> |
| 589 | 596 | |
| 590 | 597 | * <b>The [/help?cmd=all|fossil all] command</b> |
| 591 | 598 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -3,14 +3,25 @@ | |
| 3 | <h2>1.0 Don't Stress!</h2> |
| 4 | |
| 5 | If you start out using one DVCS and later decide you like the other better, |
| 6 | you can easily [./inout.wiki | move your content].¹ |
| 7 | |
| 8 | Fossil and [http://git-scm.com | Git] are very similar in many respects, |
| 9 | but they also have important differences. |
| 10 | See the table below for |
| 11 | a high-level summary and the text that follows for more details. |
| 12 | |
| 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. |
| @@ -563,28 +574,24 @@ | |
| 563 | for solving the same problem by moving to SHA-256 (a variant of the |
| 564 | [https://en.wikipedia.org/wiki/SHA-2|older SHA-2 algorithm]) and until |
| 565 | February 2019 to release a version containing the change. It's looking |
| 566 | like this will take years more to percolate through the community. |
| 567 | |
| 568 | The practical impact of SHAttered on |
| 569 | [https://en.wikipedia.org/wiki/Merkle_tree | Merkle tree] / |
| 570 | [./blockchain.md | block chain] structred data stores like Git and |
| 571 | Fossil isn't clear, but Fossil moved on the problem quickly and had a |
| 572 | widely-deployed solution to it years ago. |
| 573 | |
| 574 | |
| 575 | <h2 id="missing">3.0 Missing Features</h2> |
| 576 | |
| 577 | Most of the capabilities found in Git are also available in Fossil and |
| 578 | the other way around. For example, both systems have local check-outs, |
| 579 | remote repositories, push/pull/sync, bisect capabilities, and a "stash." |
| 580 | Both systems store project history as a directed acyclic graph (DAG) |
| 581 | of immutable check-in objects. |
| 582 | |
| 583 | There are many areas where one system has a feature that is simply |
| 584 | missing in the other, however. We covered most of those above, but there |
| 585 | are some others we haven't gotten to yet. |
| 586 | |
| 587 | |
| 588 | <h3 id="missing-in-git">3.1 Features found in Fossil but missing from Git</h3> |
| 589 | |
| 590 | * <b>The [/help?cmd=all|fossil all] command</b> |
| 591 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -3,14 +3,25 @@ | |
| 3 | <h2>1.0 Don't Stress!</h2> |
| 4 | |
| 5 | If you start out using one DVCS and later decide you like the other better, |
| 6 | you can easily [./inout.wiki | move your content].¹ |
| 7 | |
| 8 | The feature sets of Fossil and [http://git-scm.com | Git] overlap in |
| 9 | many ways. Both are |
| 10 | [https://en.wikipedia.org/wiki/Distributed_version_control | distributed |
| 11 | version control systems] managing a |
| 12 | [https://en.wikipedia.org/wiki/Directed_acyclic_graph | directed acyclic |
| 13 | graph] (DAG) of [https://en.wikipedia.org/wiki/Merkle_tree | Merkle |
| 14 | tree] / [./blockchain.md | block chain] structured check-ins to a local |
| 15 | repository clone. In both systems, new content added to the local repo |
| 16 | clone can be pushed up to a remote parent, and changes to the remote can |
| 17 | be easily pulled down to the local clone. Both systems offer bisecting, |
| 18 | private branches, a stash, etc. |
| 19 | |
| 20 | There are also, however, many important differences between these two |
| 21 | DVCSes. We summarize the major differences in the following table, then |
| 22 | detail those differences in the following text. |
| 23 | |
| 24 | Keep in mind that you are reading this on a Fossil website, and though |
| 25 | we try to be fair, the information here |
| 26 | might be biased in favor of Fossil. Ask around for second opinions from |
| 27 | people who have used <em>both</em> Fossil and Git. |
| @@ -563,28 +574,24 @@ | |
| 574 | for solving the same problem by moving to SHA-256 (a variant of the |
| 575 | [https://en.wikipedia.org/wiki/SHA-2|older SHA-2 algorithm]) and until |
| 576 | February 2019 to release a version containing the change. It's looking |
| 577 | like this will take years more to percolate through the community. |
| 578 | |
| 579 | The practical impact of SHAttered on structred data stores like the one |
| 580 | in Git and Fossil isn't clear, but you want to have your repositories |
| 581 | moved over to a stronger hash algorithm before someone figures out how |
| 582 | to make use of the weaknesses in the old one. Fossil's developers moved |
| 583 | on this problem quickly and had a widely-deployed solution to it years |
| 584 | ago. |
| 585 | |
| 586 | |
| 587 | <h2 id="missing">3.0 Missing Features</h2> |
| 588 | |
| 589 | Although there is a large overlap in capability between Fossil and Git, |
| 590 | there are many areas where one system has a feature that is simply |
| 591 | missing in the other. We covered most of those above, but there |
| 592 | are a few remaining feature differences we haven't gotten to yet. |
| 593 | |
| 594 | |
| 595 | <h3 id="missing-in-git">3.1 Features found in Fossil but missing from Git</h3> |
| 596 | |
| 597 | * <b>The [/help?cmd=all|fossil all] command</b> |
| 598 |