Fossil SCM
Fix some doc hyperlinks, and remove some long-dead ones, as suggested in [forum:5022f7b600|forum post 5022f7b600]. The git-detached-head link in that post was not fixed because the Internet Archive link to it is not working for me.
Commit
56e59a3c50565471a11b64b1fe869a125c1c8a6efb532df07ae3702b9453adec
Parent
a68a7eacd3f3f10…
5 files changed
+1
-2
+1
-1
+1
-1
+1
-1
+16
-18
+1
-2
| --- www/changes.wiki | ||
| +++ www/changes.wiki | ||
| @@ -1188,12 +1188,11 @@ | ||
| 1188 | 1188 | of rows in a timeline) are held in a cookie and thus persist |
| 1189 | 1189 | across multiple pages. |
| 1190 | 1190 | * Rework the skin editing process so that changes are implemented |
| 1191 | 1191 | on one of nine /draft pages, evaluated, then merged back to the |
| 1192 | 1192 | default. |
| 1193 | - * Added the [https://fossil-scm.org/skins/ardoise/timeline|Ardoise] | |
| 1194 | - skin. | |
| 1193 | + * Added the [/timeline?skin=ardoise&once|Ardoise] skin. | |
| 1195 | 1194 | * Fix the "fossil server" command on Unix to be much more responsive |
| 1196 | 1195 | to multiple simultaneous web requests. |
| 1197 | 1196 | * Use the IPv6 stack for the "fossil ui" and "fossil server" |
| 1198 | 1197 | commands on Windows. |
| 1199 | 1198 | * Support for [https://sqlite.org/sqlar|SQL Archives] as a download |
| 1200 | 1199 |
| --- www/changes.wiki | |
| +++ www/changes.wiki | |
| @@ -1188,12 +1188,11 @@ | |
| 1188 | of rows in a timeline) are held in a cookie and thus persist |
| 1189 | across multiple pages. |
| 1190 | * Rework the skin editing process so that changes are implemented |
| 1191 | on one of nine /draft pages, evaluated, then merged back to the |
| 1192 | default. |
| 1193 | * Added the [https://fossil-scm.org/skins/ardoise/timeline|Ardoise] |
| 1194 | skin. |
| 1195 | * Fix the "fossil server" command on Unix to be much more responsive |
| 1196 | to multiple simultaneous web requests. |
| 1197 | * Use the IPv6 stack for the "fossil ui" and "fossil server" |
| 1198 | commands on Windows. |
| 1199 | * Support for [https://sqlite.org/sqlar|SQL Archives] as a download |
| 1200 |
| --- www/changes.wiki | |
| +++ www/changes.wiki | |
| @@ -1188,12 +1188,11 @@ | |
| 1188 | of rows in a timeline) are held in a cookie and thus persist |
| 1189 | across multiple pages. |
| 1190 | * Rework the skin editing process so that changes are implemented |
| 1191 | on one of nine /draft pages, evaluated, then merged back to the |
| 1192 | default. |
| 1193 | * Added the [/timeline?skin=ardoise&once|Ardoise] skin. |
| 1194 | * Fix the "fossil server" command on Unix to be much more responsive |
| 1195 | to multiple simultaneous web requests. |
| 1196 | * Use the IPv6 stack for the "fossil ui" and "fossil server" |
| 1197 | commands on Windows. |
| 1198 | * Support for [https://sqlite.org/sqlar|SQL Archives] as a download |
| 1199 |
+1
-1
| --- www/containers.md | ||
| +++ www/containers.md | ||
| @@ -670,11 +670,11 @@ | ||
| 670 | 670 | |
| 671 | 671 | [pmmac]: https://podman.io/getting-started/installation.html#macos |
| 672 | 672 | [pmwin]: https://github.com/containers/podman/blob/main/docs/tutorials/podman-for-windows.md |
| 673 | 673 | [Podman]: https://podman.io/ |
| 674 | 674 | [rl]: https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md |
| 675 | -[whatis]: https://podman.io/whatis.html | |
| 675 | +[whatis]: https://docs.podman.io/en/latest/index.html | |
| 676 | 676 | |
| 677 | 677 | |
| 678 | 678 | ### 6.3 <a id="nspawn"></a>`systemd-container` |
| 679 | 679 | |
| 680 | 680 | If even the Podman stack is too big for you, the next-best option I’m |
| 681 | 681 |
| --- www/containers.md | |
| +++ www/containers.md | |
| @@ -670,11 +670,11 @@ | |
| 670 | |
| 671 | [pmmac]: https://podman.io/getting-started/installation.html#macos |
| 672 | [pmwin]: https://github.com/containers/podman/blob/main/docs/tutorials/podman-for-windows.md |
| 673 | [Podman]: https://podman.io/ |
| 674 | [rl]: https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md |
| 675 | [whatis]: https://podman.io/whatis.html |
| 676 | |
| 677 | |
| 678 | ### 6.3 <a id="nspawn"></a>`systemd-container` |
| 679 | |
| 680 | If even the Podman stack is too big for you, the next-best option I’m |
| 681 |
| --- www/containers.md | |
| +++ www/containers.md | |
| @@ -670,11 +670,11 @@ | |
| 670 | |
| 671 | [pmmac]: https://podman.io/getting-started/installation.html#macos |
| 672 | [pmwin]: https://github.com/containers/podman/blob/main/docs/tutorials/podman-for-windows.md |
| 673 | [Podman]: https://podman.io/ |
| 674 | [rl]: https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md |
| 675 | [whatis]: https://docs.podman.io/en/latest/index.html |
| 676 | |
| 677 | |
| 678 | ### 6.3 <a id="nspawn"></a>`systemd-container` |
| 679 | |
| 680 | If even the Podman stack is too big for you, the next-best option I’m |
| 681 |
+1
-1
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -342,11 +342,11 @@ | ||
| 342 | 342 | Fossil isn't entirely C and SQL code. Its web UI [./javascript.md | |
| 343 | 343 | uses JavaScript where |
| 344 | 344 | necessary]. The server-side |
| 345 | 345 | UI scripting uses a custom minimal |
| 346 | 346 | [https://en.wikipedia.org/wiki/Tcl|Tcl] dialect called |
| 347 | -[https://fossil-scm.org/xfer/doc/trunk/www/th1.md|TH1], which is | |
| 347 | +[./th1.md|TH1], which is | |
| 348 | 348 | embedded into Fossil itself. Fossil's build system and test suite are |
| 349 | 349 | largely based on Tcl.⁵ All of this is quite portable. |
| 350 | 350 | |
| 351 | 351 | About half of Git's code is POSIX C, and about a third is POSIX shell |
| 352 | 352 | code. This is largely why the so-called "Git for Windows" distributions |
| 353 | 353 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -342,11 +342,11 @@ | |
| 342 | Fossil isn't entirely C and SQL code. Its web UI [./javascript.md | |
| 343 | uses JavaScript where |
| 344 | necessary]. The server-side |
| 345 | UI scripting uses a custom minimal |
| 346 | [https://en.wikipedia.org/wiki/Tcl|Tcl] dialect called |
| 347 | [https://fossil-scm.org/xfer/doc/trunk/www/th1.md|TH1], which is |
| 348 | embedded into Fossil itself. Fossil's build system and test suite are |
| 349 | largely based on Tcl.⁵ All of this is quite portable. |
| 350 | |
| 351 | About half of Git's code is POSIX C, and about a third is POSIX shell |
| 352 | code. This is largely why the so-called "Git for Windows" distributions |
| 353 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -342,11 +342,11 @@ | |
| 342 | Fossil isn't entirely C and SQL code. Its web UI [./javascript.md | |
| 343 | uses JavaScript where |
| 344 | necessary]. The server-side |
| 345 | UI scripting uses a custom minimal |
| 346 | [https://en.wikipedia.org/wiki/Tcl|Tcl] dialect called |
| 347 | [./th1.md|TH1], which is |
| 348 | embedded into Fossil itself. Fossil's build system and test suite are |
| 349 | largely based on Tcl.⁵ All of this is quite portable. |
| 350 | |
| 351 | About half of Git's code is POSIX C, and about a third is POSIX shell |
| 352 | code. This is largely why the so-called "Git for Windows" distributions |
| 353 |
+1
-1
| --- www/gsoc-ideas.md | ||
| +++ www/gsoc-ideas.md | ||
| @@ -24,11 +24,11 @@ | ||
| 24 | 24 | # UI, Look and Feel |
| 25 | 25 | |
| 26 | 26 | Tasks for those interested in graphic/web design: |
| 27 | 27 | |
| 28 | 28 | * Add a quote button to the Forum, such as [discussed in this thread](https://fossil-scm.org/forum/forumpost/7ad03cd73d) |
| 29 | -* Improve the documentation history-browsing page to enable selection of 2 arbitrary versions to diff, similar to the [Mediawiki history feature enabled on Wikipedia](https://en.wikipedia.org/w/index.php?title=Fossil_(software)&action=history) | |
| 29 | +* Improve the documentation history-browsing page to enable selection of 2 arbitrary versions to diff, similar to the [Mediawiki history feature enabled on Wikipedia](https://en.wikipedia.org/w/index.php?title=Fossil_\(software\)&action=history) | |
| 30 | 30 | * Allow diffing of Forum posts |
| 31 | 31 | * General touch-ups in the existing skins. This may, depending on how deep one |
| 32 | 32 | cares to dig, require digging into C code to find, and potentially modify, how |
| 33 | 33 | the HTML is generated. |
| 34 | 34 | * Creation of one or more new skins. This does not specifically require any C |
| 35 | 35 |
| --- www/gsoc-ideas.md | |
| +++ www/gsoc-ideas.md | |
| @@ -24,11 +24,11 @@ | |
| 24 | # UI, Look and Feel |
| 25 | |
| 26 | Tasks for those interested in graphic/web design: |
| 27 | |
| 28 | * Add a quote button to the Forum, such as [discussed in this thread](https://fossil-scm.org/forum/forumpost/7ad03cd73d) |
| 29 | * Improve the documentation history-browsing page to enable selection of 2 arbitrary versions to diff, similar to the [Mediawiki history feature enabled on Wikipedia](https://en.wikipedia.org/w/index.php?title=Fossil_(software)&action=history) |
| 30 | * Allow diffing of Forum posts |
| 31 | * General touch-ups in the existing skins. This may, depending on how deep one |
| 32 | cares to dig, require digging into C code to find, and potentially modify, how |
| 33 | the HTML is generated. |
| 34 | * Creation of one or more new skins. This does not specifically require any C |
| 35 |
| --- www/gsoc-ideas.md | |
| +++ www/gsoc-ideas.md | |
| @@ -24,11 +24,11 @@ | |
| 24 | # UI, Look and Feel |
| 25 | |
| 26 | Tasks for those interested in graphic/web design: |
| 27 | |
| 28 | * Add a quote button to the Forum, such as [discussed in this thread](https://fossil-scm.org/forum/forumpost/7ad03cd73d) |
| 29 | * Improve the documentation history-browsing page to enable selection of 2 arbitrary versions to diff, similar to the [Mediawiki history feature enabled on Wikipedia](https://en.wikipedia.org/w/index.php?title=Fossil_\(software\)&action=history) |
| 30 | * Allow diffing of Forum posts |
| 31 | * General touch-ups in the existing skins. This may, depending on how deep one |
| 32 | cares to dig, require digging into C code to find, and potentially modify, how |
| 33 | the HTML is generated. |
| 34 | * Creation of one or more new skins. This does not specifically require any C |
| 35 |
+16
-18
| --- www/reviews.wiki | ||
| +++ www/reviews.wiki | ||
| @@ -35,33 +35,31 @@ | ||
| 35 | 35 | </div> |
| 36 | 36 | |
| 37 | 37 | <b>Stephan Beal writes on 2009-01-11:</b> |
| 38 | 38 | |
| 39 | 39 | <div class="indent"> |
| 40 | -Sometime in late 2007 I came across a link to fossil on | |
| 41 | -<a href="http://www.sqlite.org/">sqlite.org</a>. It | |
| 42 | -was a good thing I bookmarked it, because I was never able to find the | |
| 43 | -link again (it might have been in a bug report or something). The | |
| 44 | -reasons I first took a close look at it were (A) it stemmed from the | |
| 45 | -sqlite project, which I've held in high regards for years (e.g. I | |
| 46 | -wrote JavaScript bindings for it: | |
| 47 | -<a href="http://spiderape.sourceforge.net/plugins/sqlite/"> | |
| 48 | -http://spiderape.sourceforge.net/plugins/sqlite/</a>), and (B) it could | |
| 49 | -run as a CGI. That second point might seem a bit archaic, but in | |
| 50 | -practice CGI is the only way most hosted sites can set up a shared | |
| 51 | -source repository with multiple user IDs. (i'm not about to give out | |
| 52 | -my only account password or SSH key for my hosted sites, no matter how | |
| 53 | -much I trust the other developers, and none of my hosters allow me to | |
| 54 | -run standalone servers or add Apache modules.) | |
| 40 | +Sometime in late 2007 I came across a link to fossil on <a | |
| 41 | +href="https://sqlite.org/">sqlite.org</a>. It was a good thing I | |
| 42 | +bookmarked it, because I was never able to find the link again (it | |
| 43 | +might have been in a bug report or something). The reasons I first | |
| 44 | +took a close look at it were (A) it stemmed from the sqlite project, | |
| 45 | +which I've held in high regards for years (e.g. I wrote bindings for | |
| 46 | +it for Mozilla's SpiderMonkey JavaScript engine), and (B) it could run | |
| 47 | +as a CGI. That second point might seem a bit archaic, but in practice | |
| 48 | +CGI is the only way most hosted sites can set up a shared source | |
| 49 | +repository with multiple user IDs. (i'm not about to give out my only | |
| 50 | +account password or SSH key for my hosted sites, no matter how much I | |
| 51 | +trust the other developers, and none of my hosters allow me to run | |
| 52 | +standalone servers or add Apache modules.) | |
| 55 | 53 | |
| 56 | 54 | So I tried it out. The thing which bugged me most about it was having |
| 57 | 55 | to type "commit" or "com" instead of "ci" for checking in (as is |
| 58 | 56 | custom in all other systems I've used), despite the fact that fossil |
| 59 | 57 | uses "ci" as a filter in things like the timeline view. Looking back |
| 60 | 58 | 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. | |
| 59 | +year, in over 15 source trees, and I now get tripped up when I have to | |
| 60 | +use svn or cvs. | |
| 63 | 61 | |
| 64 | 62 | So, having got over typing "fossil com -m ...", here's why I love it so much... |
| 65 | 63 | |
| 66 | 64 | Point #1: CGI |
| 67 | 65 | |
| @@ -70,11 +68,11 @@ | ||
| 70 | 68 | (they don't belong to those projects), which I cannot host in google |
| 71 | 69 | code (because google code doesn't allow/recognize Public Domain as a |
| 72 | 70 | license, and I refuse to relicense just to accommodate them), and for |
| 73 | 71 | which SourceForge is overkill (and way too slow). With fossil I can |
| 74 | 72 | create a new repo, have it installed on my hoster |
| 75 | -(http://fossil.wanderinghorse.net), and be commiting code to it within | |
| 73 | +(https://fossil.wanderinghorse.net), and be commiting code to it within | |
| 76 | 74 | 5 minutes. |
| 77 | 75 | |
| 78 | 76 | Point #2: Wiki |
| 79 | 77 | |
| 80 | 78 | I hate wikis. I really do. Always have. They all have a different |
| 81 | 79 |
| --- www/reviews.wiki | |
| +++ www/reviews.wiki | |
| @@ -35,33 +35,31 @@ | |
| 35 | </div> |
| 36 | |
| 37 | <b>Stephan Beal writes on 2009-01-11:</b> |
| 38 | |
| 39 | <div class="indent"> |
| 40 | Sometime in late 2007 I came across a link to fossil on |
| 41 | <a href="http://www.sqlite.org/">sqlite.org</a>. It |
| 42 | was a good thing I bookmarked it, because I was never able to find the |
| 43 | link again (it might have been in a bug report or something). The |
| 44 | reasons I first took a close look at it were (A) it stemmed from the |
| 45 | sqlite project, which I've held in high regards for years (e.g. I |
| 46 | wrote JavaScript bindings for it: |
| 47 | <a href="http://spiderape.sourceforge.net/plugins/sqlite/"> |
| 48 | http://spiderape.sourceforge.net/plugins/sqlite/</a>), and (B) it could |
| 49 | run as a CGI. That second point might seem a bit archaic, but in |
| 50 | practice CGI is the only way most hosted sites can set up a shared |
| 51 | source repository with multiple user IDs. (i'm not about to give out |
| 52 | my only account password or SSH key for my hosted sites, no matter how |
| 53 | much I trust the other developers, and none of my hosters allow me to |
| 54 | run standalone servers or add Apache modules.) |
| 55 | |
| 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 | |
| @@ -70,11 +68,11 @@ | |
| 70 | (they don't belong to those projects), which I cannot host in google |
| 71 | code (because google code doesn't allow/recognize Public Domain as a |
| 72 | license, and I refuse to relicense just to accommodate them), and for |
| 73 | which SourceForge is overkill (and way too slow). With fossil I can |
| 74 | create a new repo, have it installed on my hoster |
| 75 | (http://fossil.wanderinghorse.net), and be commiting code to it within |
| 76 | 5 minutes. |
| 77 | |
| 78 | Point #2: Wiki |
| 79 | |
| 80 | I hate wikis. I really do. Always have. They all have a different |
| 81 |
| --- www/reviews.wiki | |
| +++ www/reviews.wiki | |
| @@ -35,33 +35,31 @@ | |
| 35 | </div> |
| 36 | |
| 37 | <b>Stephan Beal writes on 2009-01-11:</b> |
| 38 | |
| 39 | <div class="indent"> |
| 40 | Sometime in late 2007 I came across a link to fossil on <a |
| 41 | href="https://sqlite.org/">sqlite.org</a>. It was a good thing I |
| 42 | bookmarked it, because I was never able to find the link again (it |
| 43 | might have been in a bug report or something). The reasons I first |
| 44 | took a close look at it were (A) it stemmed from the sqlite project, |
| 45 | which I've held in high regards for years (e.g. I wrote bindings for |
| 46 | it for Mozilla's SpiderMonkey JavaScript engine), and (B) it could run |
| 47 | as a CGI. That second point might seem a bit archaic, but in practice |
| 48 | CGI is the only way most hosted sites can set up a shared source |
| 49 | repository with multiple user IDs. (i'm not about to give out my only |
| 50 | account password or SSH key for my hosted sites, no matter how much I |
| 51 | trust the other developers, and none of my hosters allow me to run |
| 52 | standalone servers or add Apache modules.) |
| 53 | |
| 54 | So I tried it out. The thing which bugged me most about it was having |
| 55 | to type "commit" or "com" instead of "ci" for checking in (as is |
| 56 | custom in all other systems I've used), despite the fact that fossil |
| 57 | uses "ci" as a filter in things like the timeline view. Looking back |
| 58 | now, I have used fossil for about about 95% of my work in the past |
| 59 | year, in over 15 source trees, and I now get tripped up when I have to |
| 60 | use svn or cvs. |
| 61 | |
| 62 | So, having got over typing "fossil com -m ...", here's why I love it so much... |
| 63 | |
| 64 | Point #1: CGI |
| 65 | |
| @@ -70,11 +68,11 @@ | |
| 68 | (they don't belong to those projects), which I cannot host in google |
| 69 | code (because google code doesn't allow/recognize Public Domain as a |
| 70 | license, and I refuse to relicense just to accommodate them), and for |
| 71 | which SourceForge is overkill (and way too slow). With fossil I can |
| 72 | create a new repo, have it installed on my hoster |
| 73 | (https://fossil.wanderinghorse.net), and be commiting code to it within |
| 74 | 5 minutes. |
| 75 | |
| 76 | Point #2: Wiki |
| 77 | |
| 78 | I hate wikis. I really do. Always have. They all have a different |
| 79 |