Fossil SCM
Replaced "countless Git users" in point about detached heads within fossil-v-git doc with a link to a Google web search that currently returns ~389000 results. So not countless at all; just very, very large. :)
Commit
e472ad36d663230b677b7b769f7ebf3e261a682cd4f0a74f8d56b809bb01467e
Parent
9dce5ffe5f3f6e1…
1 file changed
+3
-1
+3
-1
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -269,11 +269,13 @@ | ||
| 269 | 269 | Fossil DVCS]" for more details.) |
| 270 | 270 | |
| 271 | 271 | Leaf check-ins in Git that lack a "ref" become "detached," making them |
| 272 | 272 | difficult to locate and subject to garbage collection. This |
| 273 | 273 | [http://gitfaq.org/articles/what-is-a-detached-head.html|detached head |
| 274 | -state] problem has caused untold grief for countless Git users. With | |
| 274 | +state] problem has caused untold grief for | |
| 275 | +[https://www.google.com/search?q=git+detached+head+state | a huge number | |
| 276 | +of Git users]. With | |
| 275 | 277 | Fossil, detached heads are simply impossible because we can always find |
| 276 | 278 | our way back into the block chain using one or more of the relational |
| 277 | 279 | indices it automatically manages for you. |
| 278 | 280 | |
| 279 | 281 | This design difference shows up in several other places within each |
| 280 | 282 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -269,11 +269,13 @@ | |
| 269 | Fossil DVCS]" for more details.) |
| 270 | |
| 271 | Leaf check-ins in Git that lack a "ref" become "detached," making them |
| 272 | difficult to locate and subject to garbage collection. This |
| 273 | [http://gitfaq.org/articles/what-is-a-detached-head.html|detached head |
| 274 | state] problem has caused untold grief for countless Git users. With |
| 275 | Fossil, detached heads are simply impossible because we can always find |
| 276 | our way back into the block chain using one or more of the relational |
| 277 | indices it automatically manages for you. |
| 278 | |
| 279 | This design difference shows up in several other places within each |
| 280 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -269,11 +269,13 @@ | |
| 269 | Fossil DVCS]" for more details.) |
| 270 | |
| 271 | Leaf check-ins in Git that lack a "ref" become "detached," making them |
| 272 | difficult to locate and subject to garbage collection. This |
| 273 | [http://gitfaq.org/articles/what-is-a-detached-head.html|detached head |
| 274 | state] problem has caused untold grief for |
| 275 | [https://www.google.com/search?q=git+detached+head+state | a huge number |
| 276 | of Git users]. With |
| 277 | Fossil, detached heads are simply impossible because we can always find |
| 278 | our way back into the block chain using one or more of the relational |
| 279 | indices it automatically manages for you. |
| 280 | |
| 281 | This design difference shows up in several other places within each |
| 282 |