Fossil SCM
Fix some broken hyperlinks in documentation files.
Commit
a59af25f60c56da28a764a1710afb90b3808bc796443e4ff34e12e3677d17c9c
Parent
7727f9a6fbbde92…
5 files changed
+1
-2
+2
-2
+2
-2
+3
-3
+3
-3
+1
-2
| --- www/foss-cklist.wiki | ||
| +++ www/foss-cklist.wiki | ||
| @@ -2,12 +2,11 @@ | ||
| 2 | 2 | <nowiki> |
| 3 | 3 | |
| 4 | 4 | <p>This checklist is loosely derived from Tom "Spot" Callaway's Fail Score |
| 5 | 5 | blog post <a href="http://spot.livejournal.com/308370.html"> |
| 6 | 6 | http://spot.livejournal.com/308370.html</a> (see also |
| 7 | -<a href="http://www.theopensourceway.org/book/The_Open_Source_Way-How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL.html">[1]</a> and | |
| 8 | -<a href="https://www.theopensourceway.org/wiki/How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL">[2]</a>). | |
| 7 | +<a href="http://www.theopensourceway.org/book/The_Open_Source_Way-How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL.html">[1]</a>). | |
| 9 | 8 | Tom's original post assigned point scores to the various elements and |
| 10 | 9 | by adding together the individual points, the reader is supposed to be able |
| 11 | 10 | to judge the likelihood that the project will fail. |
| 12 | 11 | The point scores, and the items on the list, clearly reflect Tom's |
| 13 | 12 | biases and are not necessarily those of the larger open-source community. |
| 14 | 13 |
| --- www/foss-cklist.wiki | |
| +++ www/foss-cklist.wiki | |
| @@ -2,12 +2,11 @@ | |
| 2 | <nowiki> |
| 3 | |
| 4 | <p>This checklist is loosely derived from Tom "Spot" Callaway's Fail Score |
| 5 | blog post <a href="http://spot.livejournal.com/308370.html"> |
| 6 | http://spot.livejournal.com/308370.html</a> (see also |
| 7 | <a href="http://www.theopensourceway.org/book/The_Open_Source_Way-How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL.html">[1]</a> and |
| 8 | <a href="https://www.theopensourceway.org/wiki/How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL">[2]</a>). |
| 9 | Tom's original post assigned point scores to the various elements and |
| 10 | by adding together the individual points, the reader is supposed to be able |
| 11 | to judge the likelihood that the project will fail. |
| 12 | The point scores, and the items on the list, clearly reflect Tom's |
| 13 | biases and are not necessarily those of the larger open-source community. |
| 14 |
| --- www/foss-cklist.wiki | |
| +++ www/foss-cklist.wiki | |
| @@ -2,12 +2,11 @@ | |
| 2 | <nowiki> |
| 3 | |
| 4 | <p>This checklist is loosely derived from Tom "Spot" Callaway's Fail Score |
| 5 | blog post <a href="http://spot.livejournal.com/308370.html"> |
| 6 | http://spot.livejournal.com/308370.html</a> (see also |
| 7 | <a href="http://www.theopensourceway.org/book/The_Open_Source_Way-How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL.html">[1]</a>). |
| 8 | Tom's original post assigned point scores to the various elements and |
| 9 | by adding together the individual points, the reader is supposed to be able |
| 10 | to judge the likelihood that the project will fail. |
| 11 | The point scores, and the items on the list, clearly reflect Tom's |
| 12 | biases and are not necessarily those of the larger open-source community. |
| 13 |
+2
-2
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -283,11 +283,11 @@ | ||
| 283 | 283 | Git lets you see "what came before". Fossil makes it just as |
| 284 | 284 | easy to also see "what came after". |
| 285 | 285 | |
| 286 | 286 | Leaf check-ins in Git that lack a "ref" become "detached," making them |
| 287 | 287 | difficult to locate and subject to garbage collection. This |
| 288 | -[http://gitfaq.org/articles/what-is-a-detached-head.html|detached head | |
| 288 | +[http://gitfaq.org/1/01/what-is-a-detached-head/|detached head | |
| 289 | 289 | state] problem has caused grief for |
| 290 | 290 | [https://www.google.com/search?q=git+detached+head+state | many |
| 291 | 291 | Git users]. With |
| 292 | 292 | Fossil, detached heads are simply impossible because we can always find |
| 293 | 293 | our way back into the Merkle tree using one or more of the relations |
| @@ -509,11 +509,11 @@ | ||
| 509 | 509 | reporting on the state of the project and the work of its developers, so |
| 510 | 510 | that everyone — especially the project leader — can maintain a better |
| 511 | 511 | mental picture of what is happening, leading to better situational |
| 512 | 512 | awareness. |
| 513 | 513 | |
| 514 | -By contrast, "…[https://guides.github.com/activities/forking|forking is | |
| 514 | +By contrast, "…[https://docs.github.com/en/get-started/quickstart/contributing-to-projects|forking is | |
| 515 | 515 | at the core of social coding at GitHub]". As of January 2022, |
| 516 | 516 | [https://github.com/search?q=is:public|Github hosts 47 million distinct |
| 517 | 517 | software projects], most of which were created by forking a |
| 518 | 518 | previously-existing project. Since this is |
| 519 | 519 | [https://evansdata.com/reports/viewRelease.php?reportID=9 | roughly |
| 520 | 520 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -283,11 +283,11 @@ | |
| 283 | Git lets you see "what came before". Fossil makes it just as |
| 284 | easy to also see "what came after". |
| 285 | |
| 286 | Leaf check-ins in Git that lack a "ref" become "detached," making them |
| 287 | difficult to locate and subject to garbage collection. This |
| 288 | [http://gitfaq.org/articles/what-is-a-detached-head.html|detached head |
| 289 | state] problem has caused grief for |
| 290 | [https://www.google.com/search?q=git+detached+head+state | many |
| 291 | Git users]. With |
| 292 | Fossil, detached heads are simply impossible because we can always find |
| 293 | our way back into the Merkle tree using one or more of the relations |
| @@ -509,11 +509,11 @@ | |
| 509 | reporting on the state of the project and the work of its developers, so |
| 510 | that everyone — especially the project leader — can maintain a better |
| 511 | mental picture of what is happening, leading to better situational |
| 512 | awareness. |
| 513 | |
| 514 | By contrast, "…[https://guides.github.com/activities/forking|forking is |
| 515 | at the core of social coding at GitHub]". As of January 2022, |
| 516 | [https://github.com/search?q=is:public|Github hosts 47 million distinct |
| 517 | software projects], most of which were created by forking a |
| 518 | previously-existing project. Since this is |
| 519 | [https://evansdata.com/reports/viewRelease.php?reportID=9 | roughly |
| 520 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -283,11 +283,11 @@ | |
| 283 | Git lets you see "what came before". Fossil makes it just as |
| 284 | easy to also see "what came after". |
| 285 | |
| 286 | Leaf check-ins in Git that lack a "ref" become "detached," making them |
| 287 | difficult to locate and subject to garbage collection. This |
| 288 | [http://gitfaq.org/1/01/what-is-a-detached-head/|detached head |
| 289 | state] problem has caused grief for |
| 290 | [https://www.google.com/search?q=git+detached+head+state | many |
| 291 | Git users]. With |
| 292 | Fossil, detached heads are simply impossible because we can always find |
| 293 | our way back into the Merkle tree using one or more of the relations |
| @@ -509,11 +509,11 @@ | |
| 509 | reporting on the state of the project and the work of its developers, so |
| 510 | that everyone — especially the project leader — can maintain a better |
| 511 | mental picture of what is happening, leading to better situational |
| 512 | awareness. |
| 513 | |
| 514 | By contrast, "…[https://docs.github.com/en/get-started/quickstart/contributing-to-projects|forking is |
| 515 | at the core of social coding at GitHub]". As of January 2022, |
| 516 | [https://github.com/search?q=is:public|Github hosts 47 million distinct |
| 517 | software projects], most of which were created by forking a |
| 518 | previously-existing project. Since this is |
| 519 | [https://evansdata.com/reports/viewRelease.php?reportID=9 | roughly |
| 520 |
+2
-2
| --- www/interwiki.md | ||
| +++ www/interwiki.md | ||
| @@ -3,12 +3,12 @@ | ||
| 3 | 3 | Interwiki links are a short-hand notation for links that target |
| 4 | 4 | external wikis or websites. For example, the following two |
| 5 | 5 | hyperlinks mean the same thing (assuming an appropriate [intermap](#intermap) |
| 6 | 6 | configuration): |
| 7 | 7 | |
| 8 | - * [](wikipedia:Interwiki_links) | |
| 9 | - * [](https://en.wikipedia.org/wiki/Interwiki_links) | |
| 8 | + * [](wikipedia:MediaWiki#Interwiki_links) | |
| 9 | + * [](https://en.wikipedia.org/wiki/MediaWiki#Interwiki_links) | |
| 10 | 10 | |
| 11 | 11 | Another example: The Fossil Forum is hosted in a separate repository |
| 12 | 12 | from the Fossil source code. This page is part of the |
| 13 | 13 | source code repository. Interwiki links can be used to more easily |
| 14 | 14 | refer to the forum repository: |
| 15 | 15 |
| --- www/interwiki.md | |
| +++ www/interwiki.md | |
| @@ -3,12 +3,12 @@ | |
| 3 | Interwiki links are a short-hand notation for links that target |
| 4 | external wikis or websites. For example, the following two |
| 5 | hyperlinks mean the same thing (assuming an appropriate [intermap](#intermap) |
| 6 | configuration): |
| 7 | |
| 8 | * [](wikipedia:Interwiki_links) |
| 9 | * [](https://en.wikipedia.org/wiki/Interwiki_links) |
| 10 | |
| 11 | Another example: The Fossil Forum is hosted in a separate repository |
| 12 | from the Fossil source code. This page is part of the |
| 13 | source code repository. Interwiki links can be used to more easily |
| 14 | refer to the forum repository: |
| 15 |
| --- www/interwiki.md | |
| +++ www/interwiki.md | |
| @@ -3,12 +3,12 @@ | |
| 3 | Interwiki links are a short-hand notation for links that target |
| 4 | external wikis or websites. For example, the following two |
| 5 | hyperlinks mean the same thing (assuming an appropriate [intermap](#intermap) |
| 6 | configuration): |
| 7 | |
| 8 | * [](wikipedia:MediaWiki#Interwiki_links) |
| 9 | * [](https://en.wikipedia.org/wiki/MediaWiki#Interwiki_links) |
| 10 | |
| 11 | Another example: The Fossil Forum is hosted in a separate repository |
| 12 | from the Fossil source code. This page is part of the |
| 13 | source code repository. Interwiki links can be used to more easily |
| 14 | refer to the forum repository: |
| 15 |
+3
-3
| --- www/quotes.wiki | ||
| +++ www/quotes.wiki | ||
| @@ -19,13 +19,13 @@ | ||
| 19 | 19 | represented as n-dimensional membranes, mapping the spatial loci of |
| 20 | 20 | successive commits onto the projected manifold of each cloned |
| 21 | 21 | repository.</nowiki> |
| 22 | 22 | |
| 23 | 23 | <blockquote> |
| 24 | -<i>Previously at | |
| 25 | -[https://www.tartley.com/a-guide-to-git-using-spatial-analogies], since | |
| 26 | -removed;<br>Quoted here: [https://lwn.net/Articles/420152/].</i> | |
| 24 | +<i>by Jonathan Hartley at | |
| 25 | +[https://www.tartley.com/posts/a-guide-to-git-using-spatial-analogies]; | |
| 26 | +<br>Quoted here: [https://lwn.net/Articles/420152/].</i> | |
| 27 | 27 | </blockquote> |
| 28 | 28 | |
| 29 | 29 | <li>Git is not a Prius. Git is a Model T. |
| 30 | 30 | Its plumbing and wiring sticks out all over the place. |
| 31 | 31 | You have to be a mechanic to operate it successfully or you'll be |
| 32 | 32 |
| --- www/quotes.wiki | |
| +++ www/quotes.wiki | |
| @@ -19,13 +19,13 @@ | |
| 19 | represented as n-dimensional membranes, mapping the spatial loci of |
| 20 | successive commits onto the projected manifold of each cloned |
| 21 | repository.</nowiki> |
| 22 | |
| 23 | <blockquote> |
| 24 | <i>Previously at |
| 25 | [https://www.tartley.com/a-guide-to-git-using-spatial-analogies], since |
| 26 | removed;<br>Quoted here: [https://lwn.net/Articles/420152/].</i> |
| 27 | </blockquote> |
| 28 | |
| 29 | <li>Git is not a Prius. Git is a Model T. |
| 30 | Its plumbing and wiring sticks out all over the place. |
| 31 | You have to be a mechanic to operate it successfully or you'll be |
| 32 |
| --- www/quotes.wiki | |
| +++ www/quotes.wiki | |
| @@ -19,13 +19,13 @@ | |
| 19 | represented as n-dimensional membranes, mapping the spatial loci of |
| 20 | successive commits onto the projected manifold of each cloned |
| 21 | repository.</nowiki> |
| 22 | |
| 23 | <blockquote> |
| 24 | <i>by Jonathan Hartley at |
| 25 | [https://www.tartley.com/posts/a-guide-to-git-using-spatial-analogies]; |
| 26 | <br>Quoted here: [https://lwn.net/Articles/420152/].</i> |
| 27 | </blockquote> |
| 28 | |
| 29 | <li>Git is not a Prius. Git is a Model T. |
| 30 | Its plumbing and wiring sticks out all over the place. |
| 31 | You have to be a mechanic to operate it successfully or you'll be |
| 32 |
+3
-3
| --- www/reviews.wiki | ||
| +++ www/reviews.wiki | ||
| @@ -1,9 +1,9 @@ | ||
| 1 | 1 | <title>Reviews</title> |
| 2 | 2 | <b>External links:</b> |
| 3 | 3 | |
| 4 | - * [http://nixtu.blogspot.com/2010/03/fossil-dvcs-on-go-first-impressions.html | | |
| 4 | + * [https://www.nixtu.info/2010/03/fossil-dvcs-on-go-first-impressions.html | | |
| 5 | 5 | Fossil DVCS on the Go - First Impressions] |
| 6 | 6 | |
| 7 | 7 | <b>See Also:</b> |
| 8 | 8 | |
| 9 | 9 | * [./quotes.wiki | Short Quotes on Fossil, Git, And DVCSes] |
| @@ -56,12 +56,12 @@ | ||
| 56 | 56 | So I tried it out. The thing which bugged me most about it was having |
| 57 | 57 | to type "commit" or "com" instead of "ci" for checking in (as is |
| 58 | 58 | custom in all other systems I've used), despite the fact that fossil |
| 59 | 59 | uses "ci" as a filter in things like the timeline view. Looking back |
| 60 | 60 | now, I have used fossil for about about 95% of my work in the past |
| 61 | -year (http://blog.s11n.net/?p=71), in over 15 source trees, and I now | |
| 62 | -get tripped up when I have to use svn or cvs. | |
| 61 | +year (<a href="http://blog.s11n.net/?p=71"><i>dead link</i></a>), in | |
| 62 | +over 15 source trees, and I now get tripped up when I have to use svn or cvs. | |
| 63 | 63 | |
| 64 | 64 | So, having got over typing "fossil com -m ...", here's why I love it so much... |
| 65 | 65 | |
| 66 | 66 | Point #1: CGI |
| 67 | 67 | |
| 68 | 68 |
| --- www/reviews.wiki | |
| +++ www/reviews.wiki | |
| @@ -1,9 +1,9 @@ | |
| 1 | <title>Reviews</title> |
| 2 | <b>External links:</b> |
| 3 | |
| 4 | * [http://nixtu.blogspot.com/2010/03/fossil-dvcs-on-go-first-impressions.html | |
| 5 | Fossil DVCS on the Go - First Impressions] |
| 6 | |
| 7 | <b>See Also:</b> |
| 8 | |
| 9 | * [./quotes.wiki | Short Quotes on Fossil, Git, And DVCSes] |
| @@ -56,12 +56,12 @@ | |
| 56 | So I tried it out. The thing which bugged me most about it was having |
| 57 | to type "commit" or "com" instead of "ci" for checking in (as is |
| 58 | custom in all other systems I've used), despite the fact that fossil |
| 59 | uses "ci" as a filter in things like the timeline view. Looking back |
| 60 | now, I have used fossil for about about 95% of my work in the past |
| 61 | year (http://blog.s11n.net/?p=71), in over 15 source trees, and I now |
| 62 | get tripped up when I have to use svn or cvs. |
| 63 | |
| 64 | So, having got over typing "fossil com -m ...", here's why I love it so much... |
| 65 | |
| 66 | Point #1: CGI |
| 67 | |
| 68 |
| --- www/reviews.wiki | |
| +++ www/reviews.wiki | |
| @@ -1,9 +1,9 @@ | |
| 1 | <title>Reviews</title> |
| 2 | <b>External links:</b> |
| 3 | |
| 4 | * [https://www.nixtu.info/2010/03/fossil-dvcs-on-go-first-impressions.html | |
| 5 | Fossil DVCS on the Go - First Impressions] |
| 6 | |
| 7 | <b>See Also:</b> |
| 8 | |
| 9 | * [./quotes.wiki | Short Quotes on Fossil, Git, And DVCSes] |
| @@ -56,12 +56,12 @@ | |
| 56 | So I tried it out. The thing which bugged me most about it was having |
| 57 | to type "commit" or "com" instead of "ci" for checking in (as is |
| 58 | custom in all other systems I've used), despite the fact that fossil |
| 59 | uses "ci" as a filter in things like the timeline view. Looking back |
| 60 | now, I have used fossil for about about 95% of my work in the past |
| 61 | year (<a href="http://blog.s11n.net/?p=71"><i>dead link</i></a>), in |
| 62 | over 15 source trees, and I now get tripped up when I have to use svn or cvs. |
| 63 | |
| 64 | So, having got over typing "fossil com -m ...", here's why I love it so much... |
| 65 | |
| 66 | Point #1: CGI |
| 67 | |
| 68 |