Fossil SCM
Expanded on the point about "next" checkin in fossil-v-git doc
Commit
47e495d26b2a122618863ea4ae57cf6d4ef8c2cd51b03ee06adeb95389195c84
Parent
c5a74af45c206e5…
1 file changed
+12
-4
+12
-4
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -458,14 +458,22 @@ | ||
| 458 | 458 | |
| 459 | 459 | <h3 id="missing-in-git">3.1 Features found in Fossil but missing from Git</h3> |
| 460 | 460 | |
| 461 | 461 | * <b>The ability to show descendents of a check-in.</b> |
| 462 | 462 | |
| 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.) | |
| 463 | + Both Git and Fossil can easily find the ancestors of a check-in, but | |
| 464 | + Fossil can also quickly find the descendents for any check-in. To do | |
| 465 | + it in Git, you have to grovel through the commit log. | |
| 466 | + | |
| 467 | + This fact has many knock-on effects and shows up in several parts of | |
| 468 | + the design of each tool. It is why Fossil's | |
| 469 | + [/help?cmd=timeline|timeline] is generally easier and more clear than | |
| 470 | + those available in Git front-ends. It is why Fossil is immune from | |
| 471 | + Git's "detached head state." It's why Git has the cryptic <tt>@~</tt> | |
| 472 | + notation meaning "the parent of HEAD" (what Fossil simply | |
| 473 | + [./checkin_names.wiki|calls "prev"]) but there is no way to ask Git | |
| 474 | + for the child of the current checkin, as with "next" in Fossil. | |
| 467 | 475 | |
| 468 | 476 | * <b>Named branches</b> |
| 469 | 477 | |
| 470 | 478 | Branches in Fossil have persistent names that are propagated |
| 471 | 479 | to collaborators via [/help?cmd=push|push] and [/help?cmd=pull|pull]. |
| 472 | 480 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -458,14 +458,22 @@ | |
| 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> |
| 462 | |
| 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 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -458,14 +458,22 @@ | |
| 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> |
| 462 | |
| 463 | Both Git and Fossil can easily find the ancestors of a check-in, but |
| 464 | Fossil can also quickly find the descendents for any check-in. To do |
| 465 | it in Git, you have to grovel through the commit log. |
| 466 | |
| 467 | This fact has many knock-on effects and shows up in several parts of |
| 468 | the design of each tool. It is why Fossil's |
| 469 | [/help?cmd=timeline|timeline] is generally easier and more clear than |
| 470 | those available in Git front-ends. It is why Fossil is immune from |
| 471 | Git's "detached head state." It's why Git has the cryptic <tt>@~</tt> |
| 472 | notation meaning "the parent of HEAD" (what Fossil simply |
| 473 | [./checkin_names.wiki|calls "prev"]) but there is no way to ask Git |
| 474 | for the child of the current checkin, as with "next" in Fossil. |
| 475 | |
| 476 | * <b>Named branches</b> |
| 477 | |
| 478 | Branches in Fossil have persistent names that are propagated |
| 479 | to collaborators via [/help?cmd=push|push] and [/help?cmd=pull|pull]. |
| 480 |