Fossil SCM
Removed some points in section 3.1 of fossil-v-git (Features found in Fossil but missing from Git) which are already covered above.
Commit
c5a74af45c206e551490de0e7464f1b817fff7f0fc47a0458f5ba68c3cfda577
Parent
4c22c7056914278…
1 file changed
+5
-14
+5
-14
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -47,11 +47,12 @@ | ||
| 47 | 47 | Git provides file versioning services only, whereas Fossil adds |
| 48 | 48 | an integrated [./wikitheory.wiki | wiki], |
| 49 | 49 | [./bugtheory.wiki | ticketing & bug tracking], |
| 50 | 50 | [./embeddeddoc.wiki | embedded documentation], |
| 51 | 51 | [./event.wiki | technical notes], and a [./forum.wiki | web forum], |
| 52 | -all within a single nicely-designed [./customskin.md|skinnable web UI], | |
| 52 | +all within a single nicely-designed [./customskin.md|skinnable] web | |
| 53 | +[/help?cmd=ui|UI], | |
| 53 | 54 | protected by a fine-grained |
| 54 | 55 | [https://en.wikipedia.org/wiki/Role-based_access_control|role-based |
| 55 | 56 | access control system]. |
| 56 | 57 | These additional capabilities are available for Git as 3rd-party |
| 57 | 58 | add-ons, but with Fossil they are integrated into |
| @@ -448,12 +449,13 @@ | ||
| 448 | 449 | the other way around. For example, both systems have local check-outs, |
| 449 | 450 | remote repositories, push/pull/sync, bisect capabilities, and a "stash." |
| 450 | 451 | Both systems store project history as a directed acyclic graph (DAG) |
| 451 | 452 | of immutable check-in objects. |
| 452 | 453 | |
| 453 | -But there are a few capabilities in one system that are missing from the | |
| 454 | -other. | |
| 454 | +There are many areas where one system has a feature that is simply | |
| 455 | +missing in the other, however. We covered most of those above, but there | |
| 456 | +are some others we haven't gotten to yet. | |
| 455 | 457 | |
| 456 | 458 | |
| 457 | 459 | <h3 id="missing-in-git">3.1 Features found in Fossil but missing from Git</h3> |
| 458 | 460 | |
| 459 | 461 | * <b>The ability to show descendents of a check-in.</b> |
| @@ -461,15 +463,10 @@ | ||
| 461 | 463 | Both Git and Fossil can easily find the ancestors of a check-in. But |
| 462 | 464 | only Fossil shows the descendents. (It is possible to find the |
| 463 | 465 | descendents of a check-in in Git using the log, but that is sufficiently |
| 464 | 466 | difficult that nobody ever actually does it.) |
| 465 | 467 | |
| 466 | - * <b>Wiki, Embedded documentation, Trouble-tickets, Tech-Notes, and Forum</b> | |
| 467 | - | |
| 468 | - Git only provides versioning of source code. Fossil strives to provide | |
| 469 | - other related project management services as well. | |
| 470 | - | |
| 471 | 468 | * <b>Named branches</b> |
| 472 | 469 | |
| 473 | 470 | Branches in Fossil have persistent names that are propagated |
| 474 | 471 | to collaborators via [/help?cmd=push|push] and [/help?cmd=pull|pull]. |
| 475 | 472 | All developers see the same name on the same branch. Git, in contrast, |
| @@ -484,16 +481,10 @@ | ||
| 484 | 481 | Fossil is possible to request a pull of all repositories on a laptop |
| 485 | 482 | from their respective servers, prior to taking the laptop off network. |
| 486 | 483 | Or it is possible to do "fossil all changes" to see if there are any |
| 487 | 484 | uncommitted changes that were overlooked prior to the end of the workday. |
| 488 | 485 | |
| 489 | - * <b>The [/help?cmd=ui|fossil ui] command</b> | |
| 490 | - | |
| 491 | - Fossil supports an integrated web interface. Some of the same features | |
| 492 | - are available using third-party add-ons for Git, but they do not provide | |
| 493 | - nearly as many features and they are not nearly as convenient to use. | |
| 494 | - | |
| 495 | 486 | * <b>The [/help?cmd=undo|fossil undo] command</b> |
| 496 | 487 | |
| 497 | 488 | Whenever Fossil is told to modify the local checkout in some |
| 498 | 489 | destructive way ([/help?cmd=rm|fossil rm], [/help?cmd=update|fossil |
| 499 | 490 | update], [/help?cmd=revert|fossil revert], etc.) Fossil remembers the |
| 500 | 491 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -47,11 +47,12 @@ | |
| 47 | Git provides file versioning services only, whereas Fossil adds |
| 48 | an integrated [./wikitheory.wiki | wiki], |
| 49 | [./bugtheory.wiki | ticketing & bug tracking], |
| 50 | [./embeddeddoc.wiki | embedded documentation], |
| 51 | [./event.wiki | technical notes], and a [./forum.wiki | web forum], |
| 52 | all within a single nicely-designed [./customskin.md|skinnable web UI], |
| 53 | protected by a fine-grained |
| 54 | [https://en.wikipedia.org/wiki/Role-based_access_control|role-based |
| 55 | access control system]. |
| 56 | These additional capabilities are available for Git as 3rd-party |
| 57 | add-ons, but with Fossil they are integrated into |
| @@ -448,12 +449,13 @@ | |
| 448 | the other way around. For example, both systems have local check-outs, |
| 449 | remote repositories, push/pull/sync, bisect capabilities, and a "stash." |
| 450 | Both systems store project history as a directed acyclic graph (DAG) |
| 451 | of immutable check-in objects. |
| 452 | |
| 453 | But there are a few capabilities in one system that are missing from the |
| 454 | other. |
| 455 | |
| 456 | |
| 457 | <h3 id="missing-in-git">3.1 Features found in Fossil but missing from Git</h3> |
| 458 | |
| 459 | * <b>The ability to show descendents of a check-in.</b> |
| @@ -461,15 +463,10 @@ | |
| 461 | Both Git and Fossil can easily find the ancestors of a check-in. But |
| 462 | only Fossil shows the descendents. (It is possible to find the |
| 463 | descendents of a check-in in Git using the log, but that is sufficiently |
| 464 | difficult that nobody ever actually does it.) |
| 465 | |
| 466 | * <b>Wiki, Embedded documentation, Trouble-tickets, Tech-Notes, and Forum</b> |
| 467 | |
| 468 | Git only provides versioning of source code. Fossil strives to provide |
| 469 | other related project management services as well. |
| 470 | |
| 471 | * <b>Named branches</b> |
| 472 | |
| 473 | Branches in Fossil have persistent names that are propagated |
| 474 | to collaborators via [/help?cmd=push|push] and [/help?cmd=pull|pull]. |
| 475 | All developers see the same name on the same branch. Git, in contrast, |
| @@ -484,16 +481,10 @@ | |
| 484 | Fossil is possible to request a pull of all repositories on a laptop |
| 485 | from their respective servers, prior to taking the laptop off network. |
| 486 | Or it is possible to do "fossil all changes" to see if there are any |
| 487 | uncommitted changes that were overlooked prior to the end of the workday. |
| 488 | |
| 489 | * <b>The [/help?cmd=ui|fossil ui] command</b> |
| 490 | |
| 491 | Fossil supports an integrated web interface. Some of the same features |
| 492 | are available using third-party add-ons for Git, but they do not provide |
| 493 | nearly as many features and they are not nearly as convenient to use. |
| 494 | |
| 495 | * <b>The [/help?cmd=undo|fossil undo] command</b> |
| 496 | |
| 497 | Whenever Fossil is told to modify the local checkout in some |
| 498 | destructive way ([/help?cmd=rm|fossil rm], [/help?cmd=update|fossil |
| 499 | update], [/help?cmd=revert|fossil revert], etc.) Fossil remembers the |
| 500 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -47,11 +47,12 @@ | |
| 47 | Git provides file versioning services only, whereas Fossil adds |
| 48 | an integrated [./wikitheory.wiki | wiki], |
| 49 | [./bugtheory.wiki | ticketing & bug tracking], |
| 50 | [./embeddeddoc.wiki | embedded documentation], |
| 51 | [./event.wiki | technical notes], and a [./forum.wiki | web forum], |
| 52 | all within a single nicely-designed [./customskin.md|skinnable] web |
| 53 | [/help?cmd=ui|UI], |
| 54 | protected by a fine-grained |
| 55 | [https://en.wikipedia.org/wiki/Role-based_access_control|role-based |
| 56 | access control system]. |
| 57 | These additional capabilities are available for Git as 3rd-party |
| 58 | add-ons, but with Fossil they are integrated into |
| @@ -448,12 +449,13 @@ | |
| 449 | the other way around. For example, both systems have local check-outs, |
| 450 | remote repositories, push/pull/sync, bisect capabilities, and a "stash." |
| 451 | Both systems store project history as a directed acyclic graph (DAG) |
| 452 | of immutable check-in objects. |
| 453 | |
| 454 | There are many areas where one system has a feature that is simply |
| 455 | missing in the other, however. We covered most of those above, but there |
| 456 | are some others we haven't gotten to yet. |
| 457 | |
| 458 | |
| 459 | <h3 id="missing-in-git">3.1 Features found in Fossil but missing from Git</h3> |
| 460 | |
| 461 | * <b>The ability to show descendents of a check-in.</b> |
| @@ -461,15 +463,10 @@ | |
| 463 | Both Git and Fossil can easily find the ancestors of a check-in. But |
| 464 | only Fossil shows the descendents. (It is possible to find the |
| 465 | descendents of a check-in in Git using the log, but that is sufficiently |
| 466 | difficult that nobody ever actually does it.) |
| 467 | |
| 468 | * <b>Named branches</b> |
| 469 | |
| 470 | Branches in Fossil have persistent names that are propagated |
| 471 | to collaborators via [/help?cmd=push|push] and [/help?cmd=pull|pull]. |
| 472 | All developers see the same name on the same branch. Git, in contrast, |
| @@ -484,16 +481,10 @@ | |
| 481 | Fossil is possible to request a pull of all repositories on a laptop |
| 482 | from their respective servers, prior to taking the laptop off network. |
| 483 | Or it is possible to do "fossil all changes" to see if there are any |
| 484 | uncommitted changes that were overlooked prior to the end of the workday. |
| 485 | |
| 486 | * <b>The [/help?cmd=undo|fossil undo] command</b> |
| 487 | |
| 488 | Whenever Fossil is told to modify the local checkout in some |
| 489 | destructive way ([/help?cmd=rm|fossil rm], [/help?cmd=update|fossil |
| 490 | update], [/help?cmd=revert|fossil revert], etc.) Fossil remembers the |
| 491 |