Fossil SCM

Update the FAQ to describe how to make a clone of the self-hosting fossil repository.

drh 2009-08-28 21:36 trunk
Commit 68b73eb9b9db6028b83b576cd426fb5184a481ec
Parent 76630dd9f3883c9…
4 files changed -134 -101 +21 +21
- todo.txt - win32.txt ~ www/faq.tcl ~ www/faq.wiki
D todo.txt
-134
--- a/todo.txt
+++ b/todo.txt
@@ -1,134 +0,0 @@
1
-Bugs:
2
-
3
- * When doing an update, if a file is not found that should be there
4
- then the update aborts, only after it has written several files. It
5
- does not update your checked out version, thus when doing a fossil
6
- changes, you see everything that has come over from your update
7
- command. Steps to reproduce:
8
-
9
- $ rm src/main.c
10
- $ fossil update 9b30
11
- UPDATE ... etc ...
12
- fossil: no such file: src/main.c
13
- $ fossil info
14
- (shows version you were on prior to update)
15
- $ fossil changes
16
- EDITED ... many ...
17
-
18
- * Bug: If the server closes the socket unexpectedly, the
19
- fwrite() in http.c:103 throws a signal and kills the child
20
- process. fwrite() is not suppose to do this. Need to figure
21
- out what is going wrong.
22
-
23
- * Bug: Make sure merge and other commands (check-out) do not try
24
- to use a phantom.
25
-
26
- * Bug: When clone use incorrect http URL, local repo file is still created.
27
-
28
-Things to work on:
29
-
30
- * Use the wiki_convert() routine to render comments and other text
31
- on web pages.
32
-
33
- * If the server does not have write permission on the database
34
- file, or on the directory containing the database file (and
35
- it is thus unable to update the database because it cannot create
36
- a rollback journal) then it currently fails silently on a push.
37
- It needs to return a helpful error.
38
-
39
- * If the server returns an error (for example if the outbound /xfer
40
- message exceeds the maximum POST size of the server) the client
41
- does not report this error back to the user as it should.
42
-
43
- * The ipaddr field of the rcvfrom table is not being set. This
44
- field should be the IP address from which information is received
45
- for the local repository. So when somebody does a push of new
46
- files we record the ipaddr. Or when we do a pull, we record
47
- the ipaddr. (I think this has been fixed. Need to test.)
48
-
49
- * Additional information displayed for the "vinfo" page:
50
-
51
- + All leaves of this version that are not included in the
52
- descendant list. With date, user, comment, and hyperlink.
53
- Leaves in the descendant table should be marked as such.
54
- See the compute_leaves() function to see how to find all
55
- leaves.
56
- + Add file diff links to the file change list.
57
-
58
- * Enhancements to the diff and tkdiff commands in the cli.
59
- Allow the entire tree or a subtree to be diffed, not just a
60
- single file. Allow diffs against any two arbitrary versions,
61
- not just diffs against the current check-out.
62
-
63
- * Ticketing interface (expand this bullet)
64
-
65
- + Create new tickets as files in the file hierarchy
66
- + Append remarks to a ticket
67
- + Add attachments to a ticket
68
- + Change attributes of a ticket
69
- + Delete tickets that are no longer current. (The old
70
- content is still accessible, the ticket is just not in
71
- the current check-out.)
72
- + Server setup to define the allowed attributes and
73
- attribute values for tickets
74
- + Permanently remove malicious edits and/or attachments
75
- such as wiki-spam or warez. (Content is no longer accessible.)
76
- + View a history of all changes to a ticket
77
- + Generate reports over all tickets
78
- + Generate reports over all tickets as they existed for
79
- a chosen point in time and space.
80
- + Do full text search against the text in any single ticket or
81
- across the current versions of all tickets, or across all current
82
- and historical versions of all tickets.
83
-
84
- * Wiki interface (expand this bullet)
85
-
86
- + Create new wiki pages
87
- + Designate a single wiki page as the home page for the www interface
88
- + Designate wiki pages as read-only, append-only, or read/write.
89
- + Append comments to a wiki page
90
- + Add attachments (such as GIF images) to a wiki page
91
- + Change the content of a wiki page
92
- + Delete obsolete wiki pages. (Old content is still accessible,
93
- the page is just not on the current list of pages.)
94
- + Permanently remove malicious edits and/or attachments
95
- such as wiki-spam or warez. (Old content is no longer accessible.)
96
- + Add nofollow on external links added by unprivileged
97
- users when the link is less than N hours old.
98
- + Show the complete history of a single wiki page
99
- + Provide the ability to diff two versions of a wiki page
100
- + Show a listing of all wiki pages, both current and deleted
101
- + Do a full-text search against current versions of all wiki pages
102
- + Do a full-text search against all historical versions of a single
103
- wiki page
104
- + Do a full-text search against all historical versions of all
105
- wiki pages
106
-
107
- * Full-text search against check-in comments and diffs of each
108
- check-in.
109
-
110
- * Add a "revert" command that will undo all changes to a file
111
- or files in the current check-out - restoring the files back
112
- to their original check-out state.
113
-
114
- * Add an "annotate" command in both the cli and the www interface
115
- that will show line-by-line the most recent changes to every line
116
- in the file.
117
-
118
- * Browse the file hierarchy, similar to the "Browse" feature in
119
- CVSTrac.
120
-
121
- * Add the ability to override check-in comments. It is not possible
122
- to change the comment in the check-in itself due to the cryptographic
123
- hash. But you can add a new record to the repository that overloads
124
- a check-in comment with a new comment. Comment changes should be
125
- GPG clearsigned at the very least. Comment changes only apply if
126
- the user who made the change has the right permissions.
127
-
128
- * Make the interface to fossil look pretty and be customizable so
129
- that other people will be attracted to it, will take over maintenance
130
- of it, and we can eventually move on to other things.
131
-
132
- This has begun, but I wonder if we need to use a templating system for
133
- full customization. If the CSS is done correctly, you can change 99.9%
134
- of everything. See: http://www.csszengarden.com/
--- a/todo.txt
+++ b/todo.txt
@@ -1,134 +0,0 @@
1 Bugs:
2
3 * When doing an update, if a file is not found that should be there
4 then the update aborts, only after it has written several files. It
5 does not update your checked out version, thus when doing a fossil
6 changes, you see everything that has come over from your update
7 command. Steps to reproduce:
8
9 $ rm src/main.c
10 $ fossil update 9b30
11 UPDATE ... etc ...
12 fossil: no such file: src/main.c
13 $ fossil info
14 (shows version you were on prior to update)
15 $ fossil changes
16 EDITED ... many ...
17
18 * Bug: If the server closes the socket unexpectedly, the
19 fwrite() in http.c:103 throws a signal and kills the child
20 process. fwrite() is not suppose to do this. Need to figure
21 out what is going wrong.
22
23 * Bug: Make sure merge and other commands (check-out) do not try
24 to use a phantom.
25
26 * Bug: When clone use incorrect http URL, local repo file is still created.
27
28 Things to work on:
29
30 * Use the wiki_convert() routine to render comments and other text
31 on web pages.
32
33 * If the server does not have write permission on the database
34 file, or on the directory containing the database file (and
35 it is thus unable to update the database because it cannot create
36 a rollback journal) then it currently fails silently on a push.
37 It needs to return a helpful error.
38
39 * If the server returns an error (for example if the outbound /xfer
40 message exceeds the maximum POST size of the server) the client
41 does not report this error back to the user as it should.
42
43 * The ipaddr field of the rcvfrom table is not being set. This
44 field should be the IP address from which information is received
45 for the local repository. So when somebody does a push of new
46 files we record the ipaddr. Or when we do a pull, we record
47 the ipaddr. (I think this has been fixed. Need to test.)
48
49 * Additional information displayed for the "vinfo" page:
50
51 + All leaves of this version that are not included in the
52 descendant list. With date, user, comment, and hyperlink.
53 Leaves in the descendant table should be marked as such.
54 See the compute_leaves() function to see how to find all
55 leaves.
56 + Add file diff links to the file change list.
57
58 * Enhancements to the diff and tkdiff commands in the cli.
59 Allow the entire tree or a subtree to be diffed, not just a
60 single file. Allow diffs against any two arbitrary versions,
61 not just diffs against the current check-out.
62
63 * Ticketing interface (expand this bullet)
64
65 + Create new tickets as files in the file hierarchy
66 + Append remarks to a ticket
67 + Add attachments to a ticket
68 + Change attributes of a ticket
69 + Delete tickets that are no longer current. (The old
70 content is still accessible, the ticket is just not in
71 the current check-out.)
72 + Server setup to define the allowed attributes and
73 attribute values for tickets
74 + Permanently remove malicious edits and/or attachments
75 such as wiki-spam or warez. (Content is no longer accessible.)
76 + View a history of all changes to a ticket
77 + Generate reports over all tickets
78 + Generate reports over all tickets as they existed for
79 a chosen point in time and space.
80 + Do full text search against the text in any single ticket or
81 across the current versions of all tickets, or across all current
82 and historical versions of all tickets.
83
84 * Wiki interface (expand this bullet)
85
86 + Create new wiki pages
87 + Designate a single wiki page as the home page for the www interface
88 + Designate wiki pages as read-only, append-only, or read/write.
89 + Append comments to a wiki page
90 + Add attachments (such as GIF images) to a wiki page
91 + Change the content of a wiki page
92 + Delete obsolete wiki pages. (Old content is still accessible,
93 the page is just not on the current list of pages.)
94 + Permanently remove malicious edits and/or attachments
95 such as wiki-spam or warez. (Old content is no longer accessible.)
96 + Add nofollow on external links added by unprivileged
97 users when the link is less than N hours old.
98 + Show the complete history of a single wiki page
99 + Provide the ability to diff two versions of a wiki page
100 + Show a listing of all wiki pages, both current and deleted
101 + Do a full-text search against current versions of all wiki pages
102 + Do a full-text search against all historical versions of a single
103 wiki page
104 + Do a full-text search against all historical versions of all
105 wiki pages
106
107 * Full-text search against check-in comments and diffs of each
108 check-in.
109
110 * Add a "revert" command that will undo all changes to a file
111 or files in the current check-out - restoring the files back
112 to their original check-out state.
113
114 * Add an "annotate" command in both the cli and the www interface
115 that will show line-by-line the most recent changes to every line
116 in the file.
117
118 * Browse the file hierarchy, similar to the "Browse" feature in
119 CVSTrac.
120
121 * Add the ability to override check-in comments. It is not possible
122 to change the comment in the check-in itself due to the cryptographic
123 hash. But you can add a new record to the repository that overloads
124 a check-in comment with a new comment. Comment changes should be
125 GPG clearsigned at the very least. Comment changes only apply if
126 the user who made the change has the right permissions.
127
128 * Make the interface to fossil look pretty and be customizable so
129 that other people will be attracted to it, will take over maintenance
130 of it, and we can eventually move on to other things.
131
132 This has begun, but I wonder if we need to use a templating system for
133 full customization. If the CSS is done correctly, you can change 99.9%
134 of everything. See: http://www.csszengarden.com/
--- a/todo.txt
+++ b/todo.txt
@@ -1,134 +0,0 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
D win32.txt
-101
--- a/win32.txt
+++ b/win32.txt
@@ -1,105 +0,0 @@
1
-Fossil on Win32
2
-======================================================================
3
-
4
-Setting up the build environment:
-----------------------------------------------------------------------
5
-
6
- Install:
7
- MinGW 5.1.3
8
- MSYS 1.0.10
9
-
10
- Download/compile/install zlib (configure --prefix=/mingw)
11
- Download/compile/install tclsh (configure --prefix=/) (for tests)
12
-
13
- Installing zlib and tclsh was done in the MSYS shell so I could
14
- easily use the configure scripts. Tcl is only required to run the
15
- tests. You could install a binary distribution of Tcl/Tk and use
16
- that to run the tests, or you could opt to simply trust that
17
- everything worked and not run the tests.
18
-
19
- There is a contributed zlib package on the MinGW site.
20
-
21
- Downloading and installing a binary Tcl/Tk package and the
22
- contributed zlib package would remove the requirement of MSYS.
23
-
24
-
25
-Building on Windows:
-----------------------------------------------------------------------
26
-
27
- Ensure you have read "Setting up the build environment" first.
28
-
29
- Building is as simple as one command:
30
-
31
- C:\fossil-src> make -f Makefile.w32
32
-
33
-
34
-Outstanding Issues:
-----------------------------------------------------------------------
35
-
36
-* server is totally non-functional - #if/#end'd out of the code
37
-
38
-
39
-Commands status:
-----------------------------------------------------------------------
40
-
41
-add OK
42
-cgi Not tested
43
-changes OK
44
-checkout BAD #1
45
-clean OK
46
-clone OK
47
-close OK
48
-commit OK
49
-config OK
50
-deconstruct OK
51
-del OK
52
-descendants OK
53
-diff OK
54
-extra OK
55
-help OK
56
-http Not Tested
57
-info OK
58
-leaves OK
59
-ls OK
60
-merge OK
61
-new OK
62
-open OK
63
-pull OK
64
-push OK
65
-rebuild OK
66
-redo BAD #3
67
-rm OK
68
-server BAD #4
69
-status OK
70
-sync OK
71
-timeline OK
72
-tkdiff OK
73
-undo OK
74
-update OK
75
-user capabilities OK
76
-user default OK
77
-user list OK
78
-user new OK
79
-user password OK
80
-
81
-#1 Have a repo where I removed a file. I did a fossil checkout 123abc,
82
- which is the last version that had the file. The file does not
83
- appear. fossil checkout --force 123abc does things, but still the
84
- file does not appear.
85
-
86
- Make a new dir, fossil open ../repo.fsl && fossil checkout 123abc and
87
- the file appears.
88
-
89
- Is that normal operation?
90
-
91
-#3 In test1/ I edited a file, test2/ I updated, type file.txt changes
92
- were there. I then did fossil undo file.txt. The changes were gone
93
- and fossil status said I had edited file.txt. A fossil redo did not
94
- print anything to the screen and the changes for file.txt are not
95
- in the file. fossil status still reports that the file was edited.
96
- There was no commit/update or any other command inbetween these
97
- actions.
98
-
99
-#4 There were various difficulties in this function beyond simple socket
100
- problems. The major one being fork. This will probably be the last
101
- command to be functional in fossil on windows.
--- a/win32.txt
+++ b/win32.txt
@@ -1,105 +0,0 @@
1 Fossil on Win32
2 ======================================================================
3
4 Setting up the build environment:
-----------------------------------------------------------------------
5
6 Install:
7 MinGW 5.1.3
8 MSYS 1.0.10
9
10 Download/compile/install zlib (configure --prefix=/mingw)
11 Download/compile/install tclsh (configure --prefix=/) (for tests)
12
13 Installing zlib and tclsh was done in the MSYS shell so I could
14 easily use the configure scripts. Tcl is only required to run the
15 tests. You could install a binary distribution of Tcl/Tk and use
16 that to run the tests, or you could opt to simply trust that
17 everything worked and not run the tests.
18
19 There is a contributed zlib package on the MinGW site.
20
21 Downloading and installing a binary Tcl/Tk package and the
22 contributed zlib package would remove the requirement of MSYS.
23
24
25 Building on Windows:
-----------------------------------------------------------------------
26
27 Ensure you have read "Setting up the build environment" first.
28
29 Building is as simple as one command:
30
31 C:\fossil-src> make -f Makefile.w32
32
33
34 Outstanding Issues:
-----------------------------------------------------------------------
35
36 * server is totally non-functional - #if/#end'd out of the code
37
38
39 Commands status:
-----------------------------------------------------------------------
40
41 add OK
42 cgi Not tested
43 changes OK
44 checkout BAD #1
45 clean OK
46 clone OK
47 close OK
48 commit OK
49 config OK
50 deconstruct OK
51 del OK
52 descendants OK
53 diff OK
54 extra OK
55 help OK
56 http Not Tested
57 info OK
58 leaves OK
59 ls OK
60 merge OK
61 new OK
62 open OK
63 pull OK
64 push OK
65 rebuild OK
66 redo BAD #3
67 rm OK
68 server BAD #4
69 status OK
70 sync OK
71 timeline OK
72 tkdiff OK
73 undo OK
74 update OK
75 user capabilities OK
76 user default OK
77 user list OK
78 user new OK
79 user password OK
80
81 #1 Have a repo where I removed a file. I did a fossil checkout 123abc,
82 which is the last version that had the file. The file does not
83 appear. fossil checkout --force 123abc does things, but still the
84 file does not appear.
85
86 Make a new dir, fossil open ../repo.fsl && fossil checkout 123abc and
87 the file appears.
88
89 Is that normal operation?
90
91 #3 In test1/ I edited a file, test2/ I updated, type file.txt changes
92 were there. I then did fossil undo file.txt. The changes were gone
93 and fossil status said I had edited file.txt. A fossil redo did not
94 print anything to the screen and the changes for file.txt are not
95 in the file. fossil status still reports that the file was edited.
96 There was no commit/update or any other command inbetween these
97 actions.
98
99 #4 There were various difficulties in this function beyond simple socket
100 problems. The major one being fork. This will probably be the last
101 command to be functional in fossil on windows.
--- a/win32.txt
+++ b/win32.txt
@@ -1,105 +0,0 @@
 
 
 
 
-----------------------------------------------------------------------
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
-----------------------------------------------------------------------
 
 
 
 
 
 
 
 
 
-----------------------------------------------------------------------
 
 
 
 
 
-----------------------------------------------------------------------
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
M www/faq.tcl
+21
--- www/faq.tcl
+++ www/faq.tcl
@@ -91,10 +91,31 @@
9191
 faq {
9292
 How can I delete inappropriate content from my fossil repository?
9393
 } {
9494
 See the article on [./shunning.wiki | "shunning"] for details.
9595
 }
96
+
97
+faq {
98
+ How do I make a clone of the fossil self-hosting repository?
99
+} {
100
+ Any of the following commands should work:
101
+ <blockquote><pre>
102
+ fossil clone http://www.fossil-scm.org/ fossil.fossil<br>
103
+ fossil clone http://www2.fossil-scm.org/ fossil.fossil<br>
104
+ fossil clone http://www.hwaci.com/cgi-bin/fossil fossil.fossil
105
+ </pre></blockquote>
106
+ Once you have the repository cloned, you can open a local check-out
107
+ as follows:
108
+ <blockquote><pre>
109
+ mkdir fossil; cd fossil; fossil open ../fossil.fossil
110
+ </pre></blockquote>
111
+ Thereafter you should be able to keep your local check-out up to date
112
+ with the latest code in the public repository simply by typing:
113
+ <blockquote><pre>
114
+ fossil update
115
+ </pre></blockquote>
116
+}
96117
97118
98119
99120
 #############################################################################
100121
 # Code to actually generate the FAQ
101122
--- www/faq.tcl
+++ www/faq.tcl
@@ -91,10 +91,31 @@
91 faq {
92 How can I delete inappropriate content from my fossil repository?
93 } {
94 See the article on [./shunning.wiki | "shunning"] for details.
95 }
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
96
97
98
99 #############################################################################
100 # Code to actually generate the FAQ
101
--- www/faq.tcl
+++ www/faq.tcl
@@ -91,10 +91,31 @@
91 faq {
92 How can I delete inappropriate content from my fossil repository?
93 } {
94 See the article on [./shunning.wiki | "shunning"] for details.
95 }
96
97 faq {
98 How do I make a clone of the fossil self-hosting repository?
99 } {
100 Any of the following commands should work:
101 <blockquote><pre>
102 fossil clone http://www.fossil-scm.org/ fossil.fossil<br>
103 fossil clone http://www2.fossil-scm.org/ fossil.fossil<br>
104 fossil clone http://www.hwaci.com/cgi-bin/fossil fossil.fossil
105 </pre></blockquote>
106 Once you have the repository cloned, you can open a local check-out
107 as follows:
108 <blockquote><pre>
109 mkdir fossil; cd fossil; fossil open ../fossil.fossil
110 </pre></blockquote>
111 Thereafter you should be able to keep your local check-out up to date
112 with the latest code in the public repository simply by typing:
113 <blockquote><pre>
114 fossil update
115 </pre></blockquote>
116 }
117
118
119
120 #############################################################################
121 # Code to actually generate the FAQ
122
M www/faq.wiki
+21
--- www/faq.wiki
+++ www/faq.wiki
@@ -8,10 +8,11 @@
88
 <li><a href="#q2">What is the difference between a "branch" and a "fork"?</a></li>
99
 <li><a href="#q3">How do I create a new branch in fossil?</a></li>
1010
 <li><a href="#q4">How do I create a private branch that won't get pushed back to the
1111
 main repository.</a></li>
1212
 <li><a href="#q5">How can I delete inappropriate content from my fossil repository?</a></li>
13
+<li><a href="#q6">How do I make a clone of the fossil self-hosting repository?</a></li>
1314
 </ol>
1415
 <hr>
1516
 <a name="q1"></a>
1617
 <p><b>(1) What GUIs are available for fossil?</b></p>
1718
@@ -90,6 +91,26 @@
9091
 <a name="q5"></a>
9192
 <p><b>(5) How can I delete inappropriate content from my fossil repository?</b></p>
9293
9394
 <blockquote>See the article on [./shunning.wiki | "shunning"] for details.</blockquote></li>
9495
96
+<a name="q6"></a>
97
+<p><b>(6) How do I make a clone of the fossil self-hosting repository?</b></p>
98
+
99
+<blockquote>Any of the following commands should work:
100
+<blockquote><pre>
101
+fossil clone http://www.fossil-scm.org/ fossil.fossil<br>
102
+fossil clone http://www2.fossil-scm.org/ fossil.fossil<br>
103
+fossil clone http://www.hwaci.com/cgi-bin/fossil fossil.fossil
104
+</pre></blockquote>
105
+Once you have the repository cloned, you can open a local check-out
106
+as follows:
107
+<blockquote><pre>
108
+mkdir fossil; cd fossil; fossil open ../fossil.fossil
109
+</pre></blockquote>
110
+Thereafter you should be able to keep your local check-out up to date
111
+with the latest code in the public repository simply by typing:
112
+<blockquote><pre>
113
+fossil update
114
+</pre></blockquote></blockquote></li>
115
+
95116
 </ol>
96117
--- www/faq.wiki
+++ www/faq.wiki
@@ -8,10 +8,11 @@
8 <li><a href="#q2">What is the difference between a "branch" and a "fork"?</a></li>
9 <li><a href="#q3">How do I create a new branch in fossil?</a></li>
10 <li><a href="#q4">How do I create a private branch that won't get pushed back to the
11 main repository.</a></li>
12 <li><a href="#q5">How can I delete inappropriate content from my fossil repository?</a></li>
 
13 </ol>
14 <hr>
15 <a name="q1"></a>
16 <p><b>(1) What GUIs are available for fossil?</b></p>
17
@@ -90,6 +91,26 @@
90 <a name="q5"></a>
91 <p><b>(5) How can I delete inappropriate content from my fossil repository?</b></p>
92
93 <blockquote>See the article on [./shunning.wiki | "shunning"] for details.</blockquote></li>
94
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
95 </ol>
96
--- www/faq.wiki
+++ www/faq.wiki
@@ -8,10 +8,11 @@
8 <li><a href="#q2">What is the difference between a "branch" and a "fork"?</a></li>
9 <li><a href="#q3">How do I create a new branch in fossil?</a></li>
10 <li><a href="#q4">How do I create a private branch that won't get pushed back to the
11 main repository.</a></li>
12 <li><a href="#q5">How can I delete inappropriate content from my fossil repository?</a></li>
13 <li><a href="#q6">How do I make a clone of the fossil self-hosting repository?</a></li>
14 </ol>
15 <hr>
16 <a name="q1"></a>
17 <p><b>(1) What GUIs are available for fossil?</b></p>
18
@@ -90,6 +91,26 @@
91 <a name="q5"></a>
92 <p><b>(5) How can I delete inappropriate content from my fossil repository?</b></p>
93
94 <blockquote>See the article on [./shunning.wiki | "shunning"] for details.</blockquote></li>
95
96 <a name="q6"></a>
97 <p><b>(6) How do I make a clone of the fossil self-hosting repository?</b></p>
98
99 <blockquote>Any of the following commands should work:
100 <blockquote><pre>
101 fossil clone http://www.fossil-scm.org/ fossil.fossil<br>
102 fossil clone http://www2.fossil-scm.org/ fossil.fossil<br>
103 fossil clone http://www.hwaci.com/cgi-bin/fossil fossil.fossil
104 </pre></blockquote>
105 Once you have the repository cloned, you can open a local check-out
106 as follows:
107 <blockquote><pre>
108 mkdir fossil; cd fossil; fossil open ../fossil.fossil
109 </pre></blockquote>
110 Thereafter you should be able to keep your local check-out up to date
111 with the latest code in the public repository simply by typing:
112 <blockquote><pre>
113 fossil update
114 </pre></blockquote></blockquote></li>
115
116 </ol>
117

Keyboard Shortcuts

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