Fossil SCM

Merge in new "checkin"-to-"check-in" fixes and other documentation typo fixes.

drh 2015-03-03 13:04 trunk merge
Commit d5ef91feb8856e4a25ace3354a68d006bd5d7201
+1 -1
--- src/info.c
+++ src/info.c
@@ -227,11 +227,11 @@
227227
fossil_print("project-code: %s\n", db_get("project-code", ""));
228228
vid = g.localOpen ? db_lget_int("checkout", 0) : 0;
229229
if( vid ){
230230
show_common_info(vid, "checkout:", 1, 1);
231231
}
232
- fossil_print("checkins: %d\n",
232
+ fossil_print("check-ins: %d\n",
233233
db_int(-1, "SELECT count(*) FROM event WHERE type='ci' /*scan*/"));
234234
}else{
235235
int rid;
236236
rid = name_to_rid(g.argv[2]);
237237
if( rid==0 ){
238238
--- src/info.c
+++ src/info.c
@@ -227,11 +227,11 @@
227 fossil_print("project-code: %s\n", db_get("project-code", ""));
228 vid = g.localOpen ? db_lget_int("checkout", 0) : 0;
229 if( vid ){
230 show_common_info(vid, "checkout:", 1, 1);
231 }
232 fossil_print("checkins: %d\n",
233 db_int(-1, "SELECT count(*) FROM event WHERE type='ci' /*scan*/"));
234 }else{
235 int rid;
236 rid = name_to_rid(g.argv[2]);
237 if( rid==0 ){
238
--- src/info.c
+++ src/info.c
@@ -227,11 +227,11 @@
227 fossil_print("project-code: %s\n", db_get("project-code", ""));
228 vid = g.localOpen ? db_lget_int("checkout", 0) : 0;
229 if( vid ){
230 show_common_info(vid, "checkout:", 1, 1);
231 }
232 fossil_print("check-ins: %d\n",
233 db_int(-1, "SELECT count(*) FROM event WHERE type='ci' /*scan*/"));
234 }else{
235 int rid;
236 rid = name_to_rid(g.argv[2]);
237 if( rid==0 ){
238
+1 -1
--- src/info.c
+++ src/info.c
@@ -227,11 +227,11 @@
227227
fossil_print("project-code: %s\n", db_get("project-code", ""));
228228
vid = g.localOpen ? db_lget_int("checkout", 0) : 0;
229229
if( vid ){
230230
show_common_info(vid, "checkout:", 1, 1);
231231
}
232
- fossil_print("checkins: %d\n",
232
+ fossil_print("check-ins: %d\n",
233233
db_int(-1, "SELECT count(*) FROM event WHERE type='ci' /*scan*/"));
234234
}else{
235235
int rid;
236236
rid = name_to_rid(g.argv[2]);
237237
if( rid==0 ){
238238
--- src/info.c
+++ src/info.c
@@ -227,11 +227,11 @@
227 fossil_print("project-code: %s\n", db_get("project-code", ""));
228 vid = g.localOpen ? db_lget_int("checkout", 0) : 0;
229 if( vid ){
230 show_common_info(vid, "checkout:", 1, 1);
231 }
232 fossil_print("checkins: %d\n",
233 db_int(-1, "SELECT count(*) FROM event WHERE type='ci' /*scan*/"));
234 }else{
235 int rid;
236 rid = name_to_rid(g.argv[2]);
237 if( rid==0 ){
238
--- src/info.c
+++ src/info.c
@@ -227,11 +227,11 @@
227 fossil_print("project-code: %s\n", db_get("project-code", ""));
228 vid = g.localOpen ? db_lget_int("checkout", 0) : 0;
229 if( vid ){
230 show_common_info(vid, "checkout:", 1, 1);
231 }
232 fossil_print("check-ins: %d\n",
233 db_int(-1, "SELECT count(*) FROM event WHERE type='ci' /*scan*/"));
234 }else{
235 int rid;
236 rid = name_to_rid(g.argv[2]);
237 if( rid==0 ){
238
+1 -1
--- src/purge.c
+++ src/purge.c
@@ -571,11 +571,11 @@
571571
nArtifact = db_int(0, "SELECT count(*) FROM ok");
572572
if( explainOnly ){
573573
describe_artifacts_to_stdout("IN ok", 0);
574574
}else{
575575
int peid = purge_artifact_list("ok","",1);
576
- fossil_print("%d checkins and %d artifacts purged.\n", nCkin, nArtifact);
576
+ fossil_print("%d check-ins and %d artifacts purged.\n", nCkin, nArtifact);
577577
fossil_print("undoable using \"%s purge undo %d\".\n",
578578
g.nameOfExe, peid);
579579
}
580580
db_end_transaction(explainOnly||dryRun);
581581
}
582582
--- src/purge.c
+++ src/purge.c
@@ -571,11 +571,11 @@
571 nArtifact = db_int(0, "SELECT count(*) FROM ok");
572 if( explainOnly ){
573 describe_artifacts_to_stdout("IN ok", 0);
574 }else{
575 int peid = purge_artifact_list("ok","",1);
576 fossil_print("%d checkins and %d artifacts purged.\n", nCkin, nArtifact);
577 fossil_print("undoable using \"%s purge undo %d\".\n",
578 g.nameOfExe, peid);
579 }
580 db_end_transaction(explainOnly||dryRun);
581 }
582
--- src/purge.c
+++ src/purge.c
@@ -571,11 +571,11 @@
571 nArtifact = db_int(0, "SELECT count(*) FROM ok");
572 if( explainOnly ){
573 describe_artifacts_to_stdout("IN ok", 0);
574 }else{
575 int peid = purge_artifact_list("ok","",1);
576 fossil_print("%d check-ins and %d artifacts purged.\n", nCkin, nArtifact);
577 fossil_print("undoable using \"%s purge undo %d\".\n",
578 g.nameOfExe, peid);
579 }
580 db_end_transaction(explainOnly||dryRun);
581 }
582
+1 -1
--- src/purge.c
+++ src/purge.c
@@ -571,11 +571,11 @@
571571
nArtifact = db_int(0, "SELECT count(*) FROM ok");
572572
if( explainOnly ){
573573
describe_artifacts_to_stdout("IN ok", 0);
574574
}else{
575575
int peid = purge_artifact_list("ok","",1);
576
- fossil_print("%d checkins and %d artifacts purged.\n", nCkin, nArtifact);
576
+ fossil_print("%d check-ins and %d artifacts purged.\n", nCkin, nArtifact);
577577
fossil_print("undoable using \"%s purge undo %d\".\n",
578578
g.nameOfExe, peid);
579579
}
580580
db_end_transaction(explainOnly||dryRun);
581581
}
582582
--- src/purge.c
+++ src/purge.c
@@ -571,11 +571,11 @@
571 nArtifact = db_int(0, "SELECT count(*) FROM ok");
572 if( explainOnly ){
573 describe_artifacts_to_stdout("IN ok", 0);
574 }else{
575 int peid = purge_artifact_list("ok","",1);
576 fossil_print("%d checkins and %d artifacts purged.\n", nCkin, nArtifact);
577 fossil_print("undoable using \"%s purge undo %d\".\n",
578 g.nameOfExe, peid);
579 }
580 db_end_transaction(explainOnly||dryRun);
581 }
582
--- src/purge.c
+++ src/purge.c
@@ -571,11 +571,11 @@
571 nArtifact = db_int(0, "SELECT count(*) FROM ok");
572 if( explainOnly ){
573 describe_artifacts_to_stdout("IN ok", 0);
574 }else{
575 int peid = purge_artifact_list("ok","",1);
576 fossil_print("%d check-ins and %d artifacts purged.\n", nCkin, nArtifact);
577 fossil_print("undoable using \"%s purge undo %d\".\n",
578 g.nameOfExe, peid);
579 }
580 db_end_transaction(explainOnly||dryRun);
581 }
582
+1 -1
--- src/stat.c
+++ src/stat.c
@@ -224,11 +224,11 @@
224224
}
225225
a = t/fsize;
226226
fossil_print("%*s%d:%d\n", colWidth, "compression-ratio:", a, b);
227227
}
228228
n = db_int(0, "SELECT COUNT(*) FROM event e WHERE e.type='ci'");
229
- fossil_print("%*s%d\n", colWidth, "checkins:", n);
229
+ fossil_print("%*s%d\n", colWidth, "check-ins:", n);
230230
n = db_int(0, "SELECT count(*) FROM filename /*scan*/");
231231
fossil_print("%*s%d across all branches\n", colWidth, "files:", n);
232232
n = db_int(0, "SELECT count(*) FROM tag /*scan*/"
233233
" WHERE tagname GLOB 'wiki-*'");
234234
m = db_int(0, "SELECT COUNT(*) FROM event WHERE type='w'");
235235
--- src/stat.c
+++ src/stat.c
@@ -224,11 +224,11 @@
224 }
225 a = t/fsize;
226 fossil_print("%*s%d:%d\n", colWidth, "compression-ratio:", a, b);
227 }
228 n = db_int(0, "SELECT COUNT(*) FROM event e WHERE e.type='ci'");
229 fossil_print("%*s%d\n", colWidth, "checkins:", n);
230 n = db_int(0, "SELECT count(*) FROM filename /*scan*/");
231 fossil_print("%*s%d across all branches\n", colWidth, "files:", n);
232 n = db_int(0, "SELECT count(*) FROM tag /*scan*/"
233 " WHERE tagname GLOB 'wiki-*'");
234 m = db_int(0, "SELECT COUNT(*) FROM event WHERE type='w'");
235
--- src/stat.c
+++ src/stat.c
@@ -224,11 +224,11 @@
224 }
225 a = t/fsize;
226 fossil_print("%*s%d:%d\n", colWidth, "compression-ratio:", a, b);
227 }
228 n = db_int(0, "SELECT COUNT(*) FROM event e WHERE e.type='ci'");
229 fossil_print("%*s%d\n", colWidth, "check-ins:", n);
230 n = db_int(0, "SELECT count(*) FROM filename /*scan*/");
231 fossil_print("%*s%d across all branches\n", colWidth, "files:", n);
232 n = db_int(0, "SELECT count(*) FROM tag /*scan*/"
233 " WHERE tagname GLOB 'wiki-*'");
234 m = db_int(0, "SELECT COUNT(*) FROM event WHERE type='w'");
235
+1 -1
--- src/stat.c
+++ src/stat.c
@@ -224,11 +224,11 @@
224224
}
225225
a = t/fsize;
226226
fossil_print("%*s%d:%d\n", colWidth, "compression-ratio:", a, b);
227227
}
228228
n = db_int(0, "SELECT COUNT(*) FROM event e WHERE e.type='ci'");
229
- fossil_print("%*s%d\n", colWidth, "checkins:", n);
229
+ fossil_print("%*s%d\n", colWidth, "check-ins:", n);
230230
n = db_int(0, "SELECT count(*) FROM filename /*scan*/");
231231
fossil_print("%*s%d across all branches\n", colWidth, "files:", n);
232232
n = db_int(0, "SELECT count(*) FROM tag /*scan*/"
233233
" WHERE tagname GLOB 'wiki-*'");
234234
m = db_int(0, "SELECT COUNT(*) FROM event WHERE type='w'");
235235
--- src/stat.c
+++ src/stat.c
@@ -224,11 +224,11 @@
224 }
225 a = t/fsize;
226 fossil_print("%*s%d:%d\n", colWidth, "compression-ratio:", a, b);
227 }
228 n = db_int(0, "SELECT COUNT(*) FROM event e WHERE e.type='ci'");
229 fossil_print("%*s%d\n", colWidth, "checkins:", n);
230 n = db_int(0, "SELECT count(*) FROM filename /*scan*/");
231 fossil_print("%*s%d across all branches\n", colWidth, "files:", n);
232 n = db_int(0, "SELECT count(*) FROM tag /*scan*/"
233 " WHERE tagname GLOB 'wiki-*'");
234 m = db_int(0, "SELECT COUNT(*) FROM event WHERE type='w'");
235
--- src/stat.c
+++ src/stat.c
@@ -224,11 +224,11 @@
224 }
225 a = t/fsize;
226 fossil_print("%*s%d:%d\n", colWidth, "compression-ratio:", a, b);
227 }
228 n = db_int(0, "SELECT COUNT(*) FROM event e WHERE e.type='ci'");
229 fossil_print("%*s%d\n", colWidth, "check-ins:", n);
230 n = db_int(0, "SELECT count(*) FROM filename /*scan*/");
231 fossil_print("%*s%d across all branches\n", colWidth, "files:", n);
232 n = db_int(0, "SELECT count(*) FROM tag /*scan*/"
233 " WHERE tagname GLOB 'wiki-*'");
234 m = db_int(0, "SELECT COUNT(*) FROM event WHERE type='w'");
235
+7 -4
--- www/build.wiki
+++ www/build.wiki
@@ -33,11 +33,11 @@
3333
<em>released</em> versions of
3434
fossil are available from the <a href="http://www.fossil-scm.org/download.html">downloads page</a>.
3535
To obtain a development version of fossil, follow these steps:</p>
3636
3737
<ol>
38
-<li><p>Point your web browser at
38
+<li><p>Point your web browser to
3939
<a href="http://www.fossil-scm.org/">
4040
http://www.fossil-scm.org/</a>.</p></li>
4141
4242
<li><p>Click on the
4343
<a href="http://www.fossil-scm.org/fossil/timeline">Timeline</a>
@@ -48,11 +48,11 @@
4848
link.</p></li>
4949
5050
<li><p>Finally, click on one of the
5151
"Zip Archive" or "Tarball" links, according to your preference.
5252
These link will build a ZIP archive or a gzip-compressed tarball of the
53
-complete source code and download it to your browser.
53
+complete source code and download it to your computer.
5454
</ol>
5555
5656
<h2>Aside: Is it really safe to use an unreleased development version of
5757
the Fossil source code?</h2>
5858
@@ -66,11 +66,11 @@
6666
repository change that prevent loss-of-work due to bugs.
6767
6868
The Fossil [./selfhost.wiki | self-hosting repositories], especially
6969
the one at [http://www.fossil-scm.org/fossil], usually run a version
7070
of trunk that is less than a week or two old. Look at the bottom
71
-right-hand corner of this screen (to the right of "This page was
71
+left-hand corner of this screen (to the right of "This page was
7272
generated in...") to see exactly which version of Fossil is
7373
rendering this page. It is always safe to use whatever version
7474
of the Fossil code you find running on the main Fossil website.
7575
7676
<h2>2.0 Compiling</h2>
@@ -106,16 +106,19 @@
106106
107107
<li><p><i>Unix without running "configure"</i> → if you prefer to avoid running configure, you
108108
can also use: <b>make -f Makefile.classic</b>. You may want to make minor
109109
edits to Makefile.classic to configure the build for your system.
110110
111
-<li><p><i>MinGW/MinGW-w64</i> → Use the mingw makefile:
111
+<li><p><i>MinGW3.x (not 4.0)/MinGW-w64</i> → Use the mingw makefile:
112112
"<b>make -f win/Makefile.mingw</b>". On a Windows box you will
113113
need either Cygwin or Msys as build environment. On Cygwin, Linux
114114
or Darwin you may want to make minor edits to win/Makefile.mingw
115115
to configure the cross-compile environment.
116116
117
+Hint: don't use MinGW-4.0, it will compile but fossil won't work correctly, see
118
+<a href="https://www.fossil-scm.org/index.html/tktview/18cff45a4e210430e24c">https://www.fossil-scm.org/index.html/tktview/18cff45a4e210430e24c</a>.
119
+
117120
<li><p><i>MSVC</i> → Use the MSVC makefile. First
118121
change to the "win/" subdirectory ("<b>cd win</b>") then run
119122
"<b>nmake /f Makefile.msc</b>".<br><br>Alternatively, the batch
120123
file "<b>win\buildmsvc.bat</b>" may be used and it will attempt to
121124
detect and use the latest installed version of MSVC.<br><br>To enable
122125
--- www/build.wiki
+++ www/build.wiki
@@ -33,11 +33,11 @@
33 <em>released</em> versions of
34 fossil are available from the <a href="http://www.fossil-scm.org/download.html">downloads page</a>.
35 To obtain a development version of fossil, follow these steps:</p>
36
37 <ol>
38 <li><p>Point your web browser at
39 <a href="http://www.fossil-scm.org/">
40 http://www.fossil-scm.org/</a>.</p></li>
41
42 <li><p>Click on the
43 <a href="http://www.fossil-scm.org/fossil/timeline">Timeline</a>
@@ -48,11 +48,11 @@
48 link.</p></li>
49
50 <li><p>Finally, click on one of the
51 "Zip Archive" or "Tarball" links, according to your preference.
52 These link will build a ZIP archive or a gzip-compressed tarball of the
53 complete source code and download it to your browser.
54 </ol>
55
56 <h2>Aside: Is it really safe to use an unreleased development version of
57 the Fossil source code?</h2>
58
@@ -66,11 +66,11 @@
66 repository change that prevent loss-of-work due to bugs.
67
68 The Fossil [./selfhost.wiki | self-hosting repositories], especially
69 the one at [http://www.fossil-scm.org/fossil], usually run a version
70 of trunk that is less than a week or two old. Look at the bottom
71 right-hand corner of this screen (to the right of "This page was
72 generated in...") to see exactly which version of Fossil is
73 rendering this page. It is always safe to use whatever version
74 of the Fossil code you find running on the main Fossil website.
75
76 <h2>2.0 Compiling</h2>
@@ -106,16 +106,19 @@
106
107 <li><p><i>Unix without running "configure"</i> → if you prefer to avoid running configure, you
108 can also use: <b>make -f Makefile.classic</b>. You may want to make minor
109 edits to Makefile.classic to configure the build for your system.
110
111 <li><p><i>MinGW/MinGW-w64</i> → Use the mingw makefile:
112 "<b>make -f win/Makefile.mingw</b>". On a Windows box you will
113 need either Cygwin or Msys as build environment. On Cygwin, Linux
114 or Darwin you may want to make minor edits to win/Makefile.mingw
115 to configure the cross-compile environment.
116
 
 
 
117 <li><p><i>MSVC</i> → Use the MSVC makefile. First
118 change to the "win/" subdirectory ("<b>cd win</b>") then run
119 "<b>nmake /f Makefile.msc</b>".<br><br>Alternatively, the batch
120 file "<b>win\buildmsvc.bat</b>" may be used and it will attempt to
121 detect and use the latest installed version of MSVC.<br><br>To enable
122
--- www/build.wiki
+++ www/build.wiki
@@ -33,11 +33,11 @@
33 <em>released</em> versions of
34 fossil are available from the <a href="http://www.fossil-scm.org/download.html">downloads page</a>.
35 To obtain a development version of fossil, follow these steps:</p>
36
37 <ol>
38 <li><p>Point your web browser to
39 <a href="http://www.fossil-scm.org/">
40 http://www.fossil-scm.org/</a>.</p></li>
41
42 <li><p>Click on the
43 <a href="http://www.fossil-scm.org/fossil/timeline">Timeline</a>
@@ -48,11 +48,11 @@
48 link.</p></li>
49
50 <li><p>Finally, click on one of the
51 "Zip Archive" or "Tarball" links, according to your preference.
52 These link will build a ZIP archive or a gzip-compressed tarball of the
53 complete source code and download it to your computer.
54 </ol>
55
56 <h2>Aside: Is it really safe to use an unreleased development version of
57 the Fossil source code?</h2>
58
@@ -66,11 +66,11 @@
66 repository change that prevent loss-of-work due to bugs.
67
68 The Fossil [./selfhost.wiki | self-hosting repositories], especially
69 the one at [http://www.fossil-scm.org/fossil], usually run a version
70 of trunk that is less than a week or two old. Look at the bottom
71 left-hand corner of this screen (to the right of "This page was
72 generated in...") to see exactly which version of Fossil is
73 rendering this page. It is always safe to use whatever version
74 of the Fossil code you find running on the main Fossil website.
75
76 <h2>2.0 Compiling</h2>
@@ -106,16 +106,19 @@
106
107 <li><p><i>Unix without running "configure"</i> → if you prefer to avoid running configure, you
108 can also use: <b>make -f Makefile.classic</b>. You may want to make minor
109 edits to Makefile.classic to configure the build for your system.
110
111 <li><p><i>MinGW3.x (not 4.0)/MinGW-w64</i> → Use the mingw makefile:
112 "<b>make -f win/Makefile.mingw</b>". On a Windows box you will
113 need either Cygwin or Msys as build environment. On Cygwin, Linux
114 or Darwin you may want to make minor edits to win/Makefile.mingw
115 to configure the cross-compile environment.
116
117 Hint: don't use MinGW-4.0, it will compile but fossil won't work correctly, see
118 <a href="https://www.fossil-scm.org/index.html/tktview/18cff45a4e210430e24c">https://www.fossil-scm.org/index.html/tktview/18cff45a4e210430e24c</a>.
119
120 <li><p><i>MSVC</i> → Use the MSVC makefile. First
121 change to the "win/" subdirectory ("<b>cd win</b>") then run
122 "<b>nmake /f Makefile.msc</b>".<br><br>Alternatively, the batch
123 file "<b>win\buildmsvc.bat</b>" may be used and it will attempt to
124 detect and use the latest installed version of MSVC.<br><br>To enable
125
+7 -4
--- www/build.wiki
+++ www/build.wiki
@@ -33,11 +33,11 @@
3333
<em>released</em> versions of
3434
fossil are available from the <a href="http://www.fossil-scm.org/download.html">downloads page</a>.
3535
To obtain a development version of fossil, follow these steps:</p>
3636
3737
<ol>
38
-<li><p>Point your web browser at
38
+<li><p>Point your web browser to
3939
<a href="http://www.fossil-scm.org/">
4040
http://www.fossil-scm.org/</a>.</p></li>
4141
4242
<li><p>Click on the
4343
<a href="http://www.fossil-scm.org/fossil/timeline">Timeline</a>
@@ -48,11 +48,11 @@
4848
link.</p></li>
4949
5050
<li><p>Finally, click on one of the
5151
"Zip Archive" or "Tarball" links, according to your preference.
5252
These link will build a ZIP archive or a gzip-compressed tarball of the
53
-complete source code and download it to your browser.
53
+complete source code and download it to your computer.
5454
</ol>
5555
5656
<h2>Aside: Is it really safe to use an unreleased development version of
5757
the Fossil source code?</h2>
5858
@@ -66,11 +66,11 @@
6666
repository change that prevent loss-of-work due to bugs.
6767
6868
The Fossil [./selfhost.wiki | self-hosting repositories], especially
6969
the one at [http://www.fossil-scm.org/fossil], usually run a version
7070
of trunk that is less than a week or two old. Look at the bottom
71
-right-hand corner of this screen (to the right of "This page was
71
+left-hand corner of this screen (to the right of "This page was
7272
generated in...") to see exactly which version of Fossil is
7373
rendering this page. It is always safe to use whatever version
7474
of the Fossil code you find running on the main Fossil website.
7575
7676
<h2>2.0 Compiling</h2>
@@ -106,16 +106,19 @@
106106
107107
<li><p><i>Unix without running "configure"</i> → if you prefer to avoid running configure, you
108108
can also use: <b>make -f Makefile.classic</b>. You may want to make minor
109109
edits to Makefile.classic to configure the build for your system.
110110
111
-<li><p><i>MinGW/MinGW-w64</i> → Use the mingw makefile:
111
+<li><p><i>MinGW3.x (not 4.0)/MinGW-w64</i> → Use the mingw makefile:
112112
"<b>make -f win/Makefile.mingw</b>". On a Windows box you will
113113
need either Cygwin or Msys as build environment. On Cygwin, Linux
114114
or Darwin you may want to make minor edits to win/Makefile.mingw
115115
to configure the cross-compile environment.
116116
117
+Hint: don't use MinGW-4.0, it will compile but fossil won't work correctly, see
118
+<a href="https://www.fossil-scm.org/index.html/tktview/18cff45a4e210430e24c">https://www.fossil-scm.org/index.html/tktview/18cff45a4e210430e24c</a>.
119
+
117120
<li><p><i>MSVC</i> → Use the MSVC makefile. First
118121
change to the "win/" subdirectory ("<b>cd win</b>") then run
119122
"<b>nmake /f Makefile.msc</b>".<br><br>Alternatively, the batch
120123
file "<b>win\buildmsvc.bat</b>" may be used and it will attempt to
121124
detect and use the latest installed version of MSVC.<br><br>To enable
122125
--- www/build.wiki
+++ www/build.wiki
@@ -33,11 +33,11 @@
33 <em>released</em> versions of
34 fossil are available from the <a href="http://www.fossil-scm.org/download.html">downloads page</a>.
35 To obtain a development version of fossil, follow these steps:</p>
36
37 <ol>
38 <li><p>Point your web browser at
39 <a href="http://www.fossil-scm.org/">
40 http://www.fossil-scm.org/</a>.</p></li>
41
42 <li><p>Click on the
43 <a href="http://www.fossil-scm.org/fossil/timeline">Timeline</a>
@@ -48,11 +48,11 @@
48 link.</p></li>
49
50 <li><p>Finally, click on one of the
51 "Zip Archive" or "Tarball" links, according to your preference.
52 These link will build a ZIP archive or a gzip-compressed tarball of the
53 complete source code and download it to your browser.
54 </ol>
55
56 <h2>Aside: Is it really safe to use an unreleased development version of
57 the Fossil source code?</h2>
58
@@ -66,11 +66,11 @@
66 repository change that prevent loss-of-work due to bugs.
67
68 The Fossil [./selfhost.wiki | self-hosting repositories], especially
69 the one at [http://www.fossil-scm.org/fossil], usually run a version
70 of trunk that is less than a week or two old. Look at the bottom
71 right-hand corner of this screen (to the right of "This page was
72 generated in...") to see exactly which version of Fossil is
73 rendering this page. It is always safe to use whatever version
74 of the Fossil code you find running on the main Fossil website.
75
76 <h2>2.0 Compiling</h2>
@@ -106,16 +106,19 @@
106
107 <li><p><i>Unix without running "configure"</i> → if you prefer to avoid running configure, you
108 can also use: <b>make -f Makefile.classic</b>. You may want to make minor
109 edits to Makefile.classic to configure the build for your system.
110
111 <li><p><i>MinGW/MinGW-w64</i> → Use the mingw makefile:
112 "<b>make -f win/Makefile.mingw</b>". On a Windows box you will
113 need either Cygwin or Msys as build environment. On Cygwin, Linux
114 or Darwin you may want to make minor edits to win/Makefile.mingw
115 to configure the cross-compile environment.
116
 
 
 
117 <li><p><i>MSVC</i> → Use the MSVC makefile. First
118 change to the "win/" subdirectory ("<b>cd win</b>") then run
119 "<b>nmake /f Makefile.msc</b>".<br><br>Alternatively, the batch
120 file "<b>win\buildmsvc.bat</b>" may be used and it will attempt to
121 detect and use the latest installed version of MSVC.<br><br>To enable
122
--- www/build.wiki
+++ www/build.wiki
@@ -33,11 +33,11 @@
33 <em>released</em> versions of
34 fossil are available from the <a href="http://www.fossil-scm.org/download.html">downloads page</a>.
35 To obtain a development version of fossil, follow these steps:</p>
36
37 <ol>
38 <li><p>Point your web browser to
39 <a href="http://www.fossil-scm.org/">
40 http://www.fossil-scm.org/</a>.</p></li>
41
42 <li><p>Click on the
43 <a href="http://www.fossil-scm.org/fossil/timeline">Timeline</a>
@@ -48,11 +48,11 @@
48 link.</p></li>
49
50 <li><p>Finally, click on one of the
51 "Zip Archive" or "Tarball" links, according to your preference.
52 These link will build a ZIP archive or a gzip-compressed tarball of the
53 complete source code and download it to your computer.
54 </ol>
55
56 <h2>Aside: Is it really safe to use an unreleased development version of
57 the Fossil source code?</h2>
58
@@ -66,11 +66,11 @@
66 repository change that prevent loss-of-work due to bugs.
67
68 The Fossil [./selfhost.wiki | self-hosting repositories], especially
69 the one at [http://www.fossil-scm.org/fossil], usually run a version
70 of trunk that is less than a week or two old. Look at the bottom
71 left-hand corner of this screen (to the right of "This page was
72 generated in...") to see exactly which version of Fossil is
73 rendering this page. It is always safe to use whatever version
74 of the Fossil code you find running on the main Fossil website.
75
76 <h2>2.0 Compiling</h2>
@@ -106,16 +106,19 @@
106
107 <li><p><i>Unix without running "configure"</i> → if you prefer to avoid running configure, you
108 can also use: <b>make -f Makefile.classic</b>. You may want to make minor
109 edits to Makefile.classic to configure the build for your system.
110
111 <li><p><i>MinGW3.x (not 4.0)/MinGW-w64</i> → Use the mingw makefile:
112 "<b>make -f win/Makefile.mingw</b>". On a Windows box you will
113 need either Cygwin or Msys as build environment. On Cygwin, Linux
114 or Darwin you may want to make minor edits to win/Makefile.mingw
115 to configure the cross-compile environment.
116
117 Hint: don't use MinGW-4.0, it will compile but fossil won't work correctly, see
118 <a href="https://www.fossil-scm.org/index.html/tktview/18cff45a4e210430e24c">https://www.fossil-scm.org/index.html/tktview/18cff45a4e210430e24c</a>.
119
120 <li><p><i>MSVC</i> → Use the MSVC makefile. First
121 change to the "win/" subdirectory ("<b>cd win</b>") then run
122 "<b>nmake /f Makefile.msc</b>".<br><br>Alternatively, the batch
123 file "<b>win\buildmsvc.bat</b>" may be used and it will attempt to
124 detect and use the latest installed version of MSVC.<br><br>To enable
125
+1 -4
--- www/hints.wiki
+++ www/hints.wiki
@@ -21,14 +21,11 @@
2121
prior to going off network (for example, on a long plane ride)
2222
to make sure you have all the latest content locally. Then run
2323
"[/help/all|fossil all push]" when you get back online to upload
2424
your changes.
2525
26
- 5. Sub-menu options on Timelines lets you select either 20 or 200
27
- records. But you can manual edit the "n=" query parameter in the
28
- URL to get any number of records you desire. To see a complete
29
- timeline graph, set n to some ridiculously large value like 10000000.
26
+ 5. To see an entire timeline, type "all" into the "Max:" entry box.
3027
3128
6. You can manually add a "c=CHECKIN" query parameter to the timeline
3229
URL to get a snapshot of what was going on about the time of some
3330
check-in. The "CHECKIN" can be
3431
[./checkin_names.wiki | any valid check-in or version name], including
3532
--- www/hints.wiki
+++ www/hints.wiki
@@ -21,14 +21,11 @@
21 prior to going off network (for example, on a long plane ride)
22 to make sure you have all the latest content locally. Then run
23 "[/help/all|fossil all push]" when you get back online to upload
24 your changes.
25
26 5. Sub-menu options on Timelines lets you select either 20 or 200
27 records. But you can manual edit the "n=" query parameter in the
28 URL to get any number of records you desire. To see a complete
29 timeline graph, set n to some ridiculously large value like 10000000.
30
31 6. You can manually add a "c=CHECKIN" query parameter to the timeline
32 URL to get a snapshot of what was going on about the time of some
33 check-in. The "CHECKIN" can be
34 [./checkin_names.wiki | any valid check-in or version name], including
35
--- www/hints.wiki
+++ www/hints.wiki
@@ -21,14 +21,11 @@
21 prior to going off network (for example, on a long plane ride)
22 to make sure you have all the latest content locally. Then run
23 "[/help/all|fossil all push]" when you get back online to upload
24 your changes.
25
26 5. To see an entire timeline, type "all" into the "Max:" entry box.
 
 
 
27
28 6. You can manually add a "c=CHECKIN" query parameter to the timeline
29 URL to get a snapshot of what was going on about the time of some
30 check-in. The "CHECKIN" can be
31 [./checkin_names.wiki | any valid check-in or version name], including
32
+1 -4
--- www/hints.wiki
+++ www/hints.wiki
@@ -21,14 +21,11 @@
2121
prior to going off network (for example, on a long plane ride)
2222
to make sure you have all the latest content locally. Then run
2323
"[/help/all|fossil all push]" when you get back online to upload
2424
your changes.
2525
26
- 5. Sub-menu options on Timelines lets you select either 20 or 200
27
- records. But you can manual edit the "n=" query parameter in the
28
- URL to get any number of records you desire. To see a complete
29
- timeline graph, set n to some ridiculously large value like 10000000.
26
+ 5. To see an entire timeline, type "all" into the "Max:" entry box.
3027
3128
6. You can manually add a "c=CHECKIN" query parameter to the timeline
3229
URL to get a snapshot of what was going on about the time of some
3330
check-in. The "CHECKIN" can be
3431
[./checkin_names.wiki | any valid check-in or version name], including
3532
--- www/hints.wiki
+++ www/hints.wiki
@@ -21,14 +21,11 @@
21 prior to going off network (for example, on a long plane ride)
22 to make sure you have all the latest content locally. Then run
23 "[/help/all|fossil all push]" when you get back online to upload
24 your changes.
25
26 5. Sub-menu options on Timelines lets you select either 20 or 200
27 records. But you can manual edit the "n=" query parameter in the
28 URL to get any number of records you desire. To see a complete
29 timeline graph, set n to some ridiculously large value like 10000000.
30
31 6. You can manually add a "c=CHECKIN" query parameter to the timeline
32 URL to get a snapshot of what was going on about the time of some
33 check-in. The "CHECKIN" can be
34 [./checkin_names.wiki | any valid check-in or version name], including
35
--- www/hints.wiki
+++ www/hints.wiki
@@ -21,14 +21,11 @@
21 prior to going off network (for example, on a long plane ride)
22 to make sure you have all the latest content locally. Then run
23 "[/help/all|fossil all push]" when you get back online to upload
24 your changes.
25
26 5. To see an entire timeline, type "all" into the "Max:" entry box.
 
 
 
27
28 6. You can manually add a "c=CHECKIN" query parameter to the timeline
29 URL to get a snapshot of what was going on about the time of some
30 check-in. The "CHECKIN" can be
31 [./checkin_names.wiki | any valid check-in or version name], including
32
+1 -4
--- www/hints.wiki
+++ www/hints.wiki
@@ -21,14 +21,11 @@
2121
prior to going off network (for example, on a long plane ride)
2222
to make sure you have all the latest content locally. Then run
2323
"[/help/all|fossil all push]" when you get back online to upload
2424
your changes.
2525
26
- 5. Sub-menu options on Timelines lets you select either 20 or 200
27
- records. But you can manual edit the "n=" query parameter in the
28
- URL to get any number of records you desire. To see a complete
29
- timeline graph, set n to some ridiculously large value like 10000000.
26
+ 5. To see an entire timeline, type "all" into the "Max:" entry box.
3027
3128
6. You can manually add a "c=CHECKIN" query parameter to the timeline
3229
URL to get a snapshot of what was going on about the time of some
3330
check-in. The "CHECKIN" can be
3431
[./checkin_names.wiki | any valid check-in or version name], including
3532
--- www/hints.wiki
+++ www/hints.wiki
@@ -21,14 +21,11 @@
21 prior to going off network (for example, on a long plane ride)
22 to make sure you have all the latest content locally. Then run
23 "[/help/all|fossil all push]" when you get back online to upload
24 your changes.
25
26 5. Sub-menu options on Timelines lets you select either 20 or 200
27 records. But you can manual edit the "n=" query parameter in the
28 URL to get any number of records you desire. To see a complete
29 timeline graph, set n to some ridiculously large value like 10000000.
30
31 6. You can manually add a "c=CHECKIN" query parameter to the timeline
32 URL to get a snapshot of what was going on about the time of some
33 check-in. The "CHECKIN" can be
34 [./checkin_names.wiki | any valid check-in or version name], including
35
--- www/hints.wiki
+++ www/hints.wiki
@@ -21,14 +21,11 @@
21 prior to going off network (for example, on a long plane ride)
22 to make sure you have all the latest content locally. Then run
23 "[/help/all|fossil all push]" when you get back online to upload
24 your changes.
25
26 5. To see an entire timeline, type "all" into the "Max:" entry box.
 
 
 
27
28 6. You can manually add a "c=CHECKIN" query parameter to the timeline
29 URL to get a snapshot of what was going on about the time of some
30 check-in. The "CHECKIN" can be
31 [./checkin_names.wiki | any valid check-in or version name], including
32
+18 -1
--- www/server.wiki
+++ www/server.wiki
@@ -53,11 +53,11 @@
5353
</blockquote>
5454
<a name="inetd"></a>
5555
<h2>Fossil as an inetd/xinetd or stunnel service</h2><blockquote>
5656
<p>
5757
A Fossil server can be launched on-demand by inetd or xinetd using
58
-the [/help/http|fossil http] command. To launch Fossil from inetd, modify
58
+the [/help/http|fossil http] command. To launch Fossil from inetd, modify
5959
your inetd configuration file (typically "/etc/inetd.conf") to contain a
6060
line something like this:
6161
<blockquote>
6262
<pre>
6363
12345 stream tcp nowait.1000 root /usr/bin/fossil /usr/bin/fossil http /home/fossil/repo.fossil
@@ -69,10 +69,23 @@
6969
Obviously you will
7070
need to modify the pathnames for your particular setup.
7171
The final argument is either the name of the fossil repository to be served,
7272
or a directory containing multiple repositories.
7373
</p>
74
+<p>
75
+For systems where the port-specification must be a symbolic name and cannot be
76
+numeric, add the desired name and port to /etc/services, e.g.:
77
+<blockquote>
78
+<pre>
79
+fossil 12345/tcp #fossil server
80
+</pre>
81
+</blockquote>
82
+and use the symbolic name ('fossil' in this example) instead of the numeral ('12345')
83
+in inetd.conf. For details, see the relevant section in your system's documentation, e.g.
84
+the [https://www.freebsd.org/doc/en/books/handbook/network-inetd.html|FreeBSD Handbook] in
85
+case you use FreeBSD.
86
+</p>
7487
<p>
7588
If your system is running xinetd, then the configuration is likely to be
7689
in the file "/etc/xinetd.conf" or in a subfile of "/etc/xinetd.d".
7790
An xinetd configuration file will appear like this:</p>
7891
<blockquote>
@@ -96,10 +109,14 @@
96109
In both cases notice that Fossil was launched as root. This is not required,
97110
but if it is done, then Fossil will automatically put itself into a chroot
98111
jail for the user who owns the fossil repository before reading any information
99112
off of the wire.
100113
</p>
114
+<p>
115
+Inetd or xinetd must be enabled, and must be (re)started whenever their configuration
116
+changes - consult your system's documentation for details.
117
+</p>
101118
<p>
102119
[https://www.stunnel.org/ | Stunnel version 5] is an inetd-like process that
103120
accepts and decodes SSL-encrypted connections. Fossil can be run directly from
104121
stunnel in a manner similar to inetd and xinetd. This can be used to provide
105122
a secure link to a Fossil project. The configuration needed to get stunnel5
106123
--- www/server.wiki
+++ www/server.wiki
@@ -53,11 +53,11 @@
53 </blockquote>
54 <a name="inetd"></a>
55 <h2>Fossil as an inetd/xinetd or stunnel service</h2><blockquote>
56 <p>
57 A Fossil server can be launched on-demand by inetd or xinetd using
58 the [/help/http|fossil http] command. To launch Fossil from inetd, modify
59 your inetd configuration file (typically "/etc/inetd.conf") to contain a
60 line something like this:
61 <blockquote>
62 <pre>
63 12345 stream tcp nowait.1000 root /usr/bin/fossil /usr/bin/fossil http /home/fossil/repo.fossil
@@ -69,10 +69,23 @@
69 Obviously you will
70 need to modify the pathnames for your particular setup.
71 The final argument is either the name of the fossil repository to be served,
72 or a directory containing multiple repositories.
73 </p>
 
 
 
 
 
 
 
 
 
 
 
 
 
74 <p>
75 If your system is running xinetd, then the configuration is likely to be
76 in the file "/etc/xinetd.conf" or in a subfile of "/etc/xinetd.d".
77 An xinetd configuration file will appear like this:</p>
78 <blockquote>
@@ -96,10 +109,14 @@
96 In both cases notice that Fossil was launched as root. This is not required,
97 but if it is done, then Fossil will automatically put itself into a chroot
98 jail for the user who owns the fossil repository before reading any information
99 off of the wire.
100 </p>
 
 
 
 
101 <p>
102 [https://www.stunnel.org/ | Stunnel version 5] is an inetd-like process that
103 accepts and decodes SSL-encrypted connections. Fossil can be run directly from
104 stunnel in a manner similar to inetd and xinetd. This can be used to provide
105 a secure link to a Fossil project. The configuration needed to get stunnel5
106
--- www/server.wiki
+++ www/server.wiki
@@ -53,11 +53,11 @@
53 </blockquote>
54 <a name="inetd"></a>
55 <h2>Fossil as an inetd/xinetd or stunnel service</h2><blockquote>
56 <p>
57 A Fossil server can be launched on-demand by inetd or xinetd using
58 the [/help/http|fossil http] command. To launch Fossil from inetd, modify
59 your inetd configuration file (typically "/etc/inetd.conf") to contain a
60 line something like this:
61 <blockquote>
62 <pre>
63 12345 stream tcp nowait.1000 root /usr/bin/fossil /usr/bin/fossil http /home/fossil/repo.fossil
@@ -69,10 +69,23 @@
69 Obviously you will
70 need to modify the pathnames for your particular setup.
71 The final argument is either the name of the fossil repository to be served,
72 or a directory containing multiple repositories.
73 </p>
74 <p>
75 For systems where the port-specification must be a symbolic name and cannot be
76 numeric, add the desired name and port to /etc/services, e.g.:
77 <blockquote>
78 <pre>
79 fossil 12345/tcp #fossil server
80 </pre>
81 </blockquote>
82 and use the symbolic name ('fossil' in this example) instead of the numeral ('12345')
83 in inetd.conf. For details, see the relevant section in your system's documentation, e.g.
84 the [https://www.freebsd.org/doc/en/books/handbook/network-inetd.html|FreeBSD Handbook] in
85 case you use FreeBSD.
86 </p>
87 <p>
88 If your system is running xinetd, then the configuration is likely to be
89 in the file "/etc/xinetd.conf" or in a subfile of "/etc/xinetd.d".
90 An xinetd configuration file will appear like this:</p>
91 <blockquote>
@@ -96,10 +109,14 @@
109 In both cases notice that Fossil was launched as root. This is not required,
110 but if it is done, then Fossil will automatically put itself into a chroot
111 jail for the user who owns the fossil repository before reading any information
112 off of the wire.
113 </p>
114 <p>
115 Inetd or xinetd must be enabled, and must be (re)started whenever their configuration
116 changes - consult your system's documentation for details.
117 </p>
118 <p>
119 [https://www.stunnel.org/ | Stunnel version 5] is an inetd-like process that
120 accepts and decodes SSL-encrypted connections. Fossil can be run directly from
121 stunnel in a manner similar to inetd and xinetd. This can be used to provide
122 a secure link to a Fossil project. The configuration needed to get stunnel5
123
+18 -1
--- www/server.wiki
+++ www/server.wiki
@@ -53,11 +53,11 @@
5353
</blockquote>
5454
<a name="inetd"></a>
5555
<h2>Fossil as an inetd/xinetd or stunnel service</h2><blockquote>
5656
<p>
5757
A Fossil server can be launched on-demand by inetd or xinetd using
58
-the [/help/http|fossil http] command. To launch Fossil from inetd, modify
58
+the [/help/http|fossil http] command. To launch Fossil from inetd, modify
5959
your inetd configuration file (typically "/etc/inetd.conf") to contain a
6060
line something like this:
6161
<blockquote>
6262
<pre>
6363
12345 stream tcp nowait.1000 root /usr/bin/fossil /usr/bin/fossil http /home/fossil/repo.fossil
@@ -69,10 +69,23 @@
6969
Obviously you will
7070
need to modify the pathnames for your particular setup.
7171
The final argument is either the name of the fossil repository to be served,
7272
or a directory containing multiple repositories.
7373
</p>
74
+<p>
75
+For systems where the port-specification must be a symbolic name and cannot be
76
+numeric, add the desired name and port to /etc/services, e.g.:
77
+<blockquote>
78
+<pre>
79
+fossil 12345/tcp #fossil server
80
+</pre>
81
+</blockquote>
82
+and use the symbolic name ('fossil' in this example) instead of the numeral ('12345')
83
+in inetd.conf. For details, see the relevant section in your system's documentation, e.g.
84
+the [https://www.freebsd.org/doc/en/books/handbook/network-inetd.html|FreeBSD Handbook] in
85
+case you use FreeBSD.
86
+</p>
7487
<p>
7588
If your system is running xinetd, then the configuration is likely to be
7689
in the file "/etc/xinetd.conf" or in a subfile of "/etc/xinetd.d".
7790
An xinetd configuration file will appear like this:</p>
7891
<blockquote>
@@ -96,10 +109,14 @@
96109
In both cases notice that Fossil was launched as root. This is not required,
97110
but if it is done, then Fossil will automatically put itself into a chroot
98111
jail for the user who owns the fossil repository before reading any information
99112
off of the wire.
100113
</p>
114
+<p>
115
+Inetd or xinetd must be enabled, and must be (re)started whenever their configuration
116
+changes - consult your system's documentation for details.
117
+</p>
101118
<p>
102119
[https://www.stunnel.org/ | Stunnel version 5] is an inetd-like process that
103120
accepts and decodes SSL-encrypted connections. Fossil can be run directly from
104121
stunnel in a manner similar to inetd and xinetd. This can be used to provide
105122
a secure link to a Fossil project. The configuration needed to get stunnel5
106123
--- www/server.wiki
+++ www/server.wiki
@@ -53,11 +53,11 @@
53 </blockquote>
54 <a name="inetd"></a>
55 <h2>Fossil as an inetd/xinetd or stunnel service</h2><blockquote>
56 <p>
57 A Fossil server can be launched on-demand by inetd or xinetd using
58 the [/help/http|fossil http] command. To launch Fossil from inetd, modify
59 your inetd configuration file (typically "/etc/inetd.conf") to contain a
60 line something like this:
61 <blockquote>
62 <pre>
63 12345 stream tcp nowait.1000 root /usr/bin/fossil /usr/bin/fossil http /home/fossil/repo.fossil
@@ -69,10 +69,23 @@
69 Obviously you will
70 need to modify the pathnames for your particular setup.
71 The final argument is either the name of the fossil repository to be served,
72 or a directory containing multiple repositories.
73 </p>
 
 
 
 
 
 
 
 
 
 
 
 
 
74 <p>
75 If your system is running xinetd, then the configuration is likely to be
76 in the file "/etc/xinetd.conf" or in a subfile of "/etc/xinetd.d".
77 An xinetd configuration file will appear like this:</p>
78 <blockquote>
@@ -96,10 +109,14 @@
96 In both cases notice that Fossil was launched as root. This is not required,
97 but if it is done, then Fossil will automatically put itself into a chroot
98 jail for the user who owns the fossil repository before reading any information
99 off of the wire.
100 </p>
 
 
 
 
101 <p>
102 [https://www.stunnel.org/ | Stunnel version 5] is an inetd-like process that
103 accepts and decodes SSL-encrypted connections. Fossil can be run directly from
104 stunnel in a manner similar to inetd and xinetd. This can be used to provide
105 a secure link to a Fossil project. The configuration needed to get stunnel5
106
--- www/server.wiki
+++ www/server.wiki
@@ -53,11 +53,11 @@
53 </blockquote>
54 <a name="inetd"></a>
55 <h2>Fossil as an inetd/xinetd or stunnel service</h2><blockquote>
56 <p>
57 A Fossil server can be launched on-demand by inetd or xinetd using
58 the [/help/http|fossil http] command. To launch Fossil from inetd, modify
59 your inetd configuration file (typically "/etc/inetd.conf") to contain a
60 line something like this:
61 <blockquote>
62 <pre>
63 12345 stream tcp nowait.1000 root /usr/bin/fossil /usr/bin/fossil http /home/fossil/repo.fossil
@@ -69,10 +69,23 @@
69 Obviously you will
70 need to modify the pathnames for your particular setup.
71 The final argument is either the name of the fossil repository to be served,
72 or a directory containing multiple repositories.
73 </p>
74 <p>
75 For systems where the port-specification must be a symbolic name and cannot be
76 numeric, add the desired name and port to /etc/services, e.g.:
77 <blockquote>
78 <pre>
79 fossil 12345/tcp #fossil server
80 </pre>
81 </blockquote>
82 and use the symbolic name ('fossil' in this example) instead of the numeral ('12345')
83 in inetd.conf. For details, see the relevant section in your system's documentation, e.g.
84 the [https://www.freebsd.org/doc/en/books/handbook/network-inetd.html|FreeBSD Handbook] in
85 case you use FreeBSD.
86 </p>
87 <p>
88 If your system is running xinetd, then the configuration is likely to be
89 in the file "/etc/xinetd.conf" or in a subfile of "/etc/xinetd.d".
90 An xinetd configuration file will appear like this:</p>
91 <blockquote>
@@ -96,10 +109,14 @@
109 In both cases notice that Fossil was launched as root. This is not required,
110 but if it is done, then Fossil will automatically put itself into a chroot
111 jail for the user who owns the fossil repository before reading any information
112 off of the wire.
113 </p>
114 <p>
115 Inetd or xinetd must be enabled, and must be (re)started whenever their configuration
116 changes - consult your system's documentation for details.
117 </p>
118 <p>
119 [https://www.stunnel.org/ | Stunnel version 5] is an inetd-like process that
120 accepts and decodes SSL-encrypted connections. Fossil can be run directly from
121 stunnel in a manner similar to inetd and xinetd. This can be used to provide
122 a secure link to a Fossil project. The configuration needed to get stunnel5
123

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button