Fossil SCM

Documentation updates: Added FAQ and testimonials.

drh 2009-01-25 21:16 trunk
Commit 627de3bf16b0552bbed7b62496d2f82ac4f14b7d
Parent 9be1b00392a940f…
5 files changed +46 +12 +6 -4 +2 +90
+ www/faq.tcl + www/faq.wiki ~ www/index.wiki ~ www/qandc.wiki + www/reviews.wiki
A www/faq.tcl
+46
--- a/www/faq.tcl
+++ b/www/faq.tcl
@@ -0,0 +1,46 @@
1
+#!/usr/bin/tclsh
2
+#
3
+# Run this to generate the FAQ
4
+#
5
+set cnt 1
6
+proc faq {question answer} {
7
+ set ::faq($::cnt) [list [string trim $question] [string trim $answer]]
8
+ incr ::cnt
9
+}
10
+
11
+faq {
12
+ What GUIs are available for fossil?
13
+} {
14
+ The fossil executable comes with a web-based GUI built in. Just run
15
+faq {
16
+ How donch] new</b> <iui>
17
+ <b>fossil [/help/ui|ui]</b> <i>REPOSITORY-FILENAME</i>
18
+ </blockquote>
19
+
20
+ And your default web browser should pop up and automatically point to
21
+ the fossil interface. (Hint: You can omit the <i>REPOSITORY-FILENAME</i>
22
+ if you are within an open check-out.)
23
+}
24
+
25
+faq {
26
+ What is the difference between a "branch" and a "fork"?
27
+} {
28
+ This is a big question - too big to answer in a FAQ. Please
29
+ ad the <a href="branching.wiki">Branching, Forking, Merging,
30
+ and Tagging</a> in fossil {
31
+ There are lots of ways:
32
+
33
+ When you are checking in a new change using the <b>[/hcommit>
34
+ command, you can add the option "--branch <i>BRANCH-NAME</i>" to
35
+ make the newchange be the foundingfounding check-ineck-inblockquot document.
36
+}
37
+
38
+
39
+faq {
40
+ How donch] new</b> <i>BRblockquot
41
+ The <i>BRANCbranch>BRANCH-NAME</i> argument is the name of the new branch and the
42
+ <i>BASIS</i> argument is the name of the check-in that the branch splits
43
+ off from.
44
+
45
+ If you already have a fork in your check-in tree and you want to convert
46
+ that fork to a branch, you can do this from the web interf
--- a/www/faq.tcl
+++ b/www/faq.tcl
@@ -0,0 +1,46 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
--- a/www/faq.tcl
+++ b/www/faq.tcl
@@ -0,0 +1,46 @@
1 #!/usr/bin/tclsh
2 #
3 # Run this to generate the FAQ
4 #
5 set cnt 1
6 proc faq {question answer} {
7 set ::faq($::cnt) [list [string trim $question] [string trim $answer]]
8 incr ::cnt
9 }
10
11 faq {
12 What GUIs are available for fossil?
13 } {
14 The fossil executable comes with a web-based GUI built in. Just run
15 faq {
16 How donch] new</b> <iui>
17 <b>fossil [/help/ui|ui]</b> <i>REPOSITORY-FILENAME</i>
18 </blockquote>
19
20 And your default web browser should pop up and automatically point to
21 the fossil interface. (Hint: You can omit the <i>REPOSITORY-FILENAME</i>
22 if you are within an open check-out.)
23 }
24
25 faq {
26 What is the difference between a "branch" and a "fork"?
27 } {
28 This is a big question - too big to answer in a FAQ. Please
29 ad the <a href="branching.wiki">Branching, Forking, Merging,
30 and Tagging</a> in fossil {
31 There are lots of ways:
32
33 When you are checking in a new change using the <b>[/hcommit>
34 command, you can add the option "--branch <i>BRANCH-NAME</i>" to
35 make the newchange be the foundingfounding check-ineck-inblockquot document.
36 }
37
38
39 faq {
40 How donch] new</b> <i>BRblockquot
41 The <i>BRANCbranch>BRANCH-NAME</i> argument is the name of the new branch and the
42 <i>BASIS</i> argument is the name of the check-in that the branch splits
43 off from.
44
45 If you already have a fork in your check-in tree and you want to convert
46 that fork to a branch, you can do this from the web interf
A www/faq.wiki
+12
--- a/www/faq.wiki
+++ b/www/faq.wiki
@@ -0,0 +1,12 @@
1
+"--bgcolor <i>COLOR</i>" option to give the branch a
2
+specific ba<me<br><br>3.fossli in fossil4">6web-based GUI built in. ui incommitchange be the foundingfounding check-inbranchfoundingaific ba<me<br><br>3.fossli<me Y clone clone http://wwwopenupdate/ol>
3
+efossil; cd fossilsimpl/ol>
4
+appeartion to give the branch a
5
+specific ba<me<br><br>3.fossli in fossil4">6web-based GUI built in. ui "--bgco
6
+/ol>
7
+You cannot. All branches in fossil are public in the sense that
8
+are all pushed and pulled together. There is no way to tell fossil
9
+to only push or pull a subset of branches.
10
+
11
+Of course, as long as you never push, you can make as many private
12
+changes as you want.
--- a/www/faq.wiki
+++ b/www/faq.wiki
@@ -0,0 +1,12 @@
 
 
 
 
 
 
 
 
 
 
 
 
--- a/www/faq.wiki
+++ b/www/faq.wiki
@@ -0,0 +1,12 @@
1 "--bgcolor <i>COLOR</i>" option to give the branch a
2 specific ba<me<br><br>3.fossli in fossil4">6web-based GUI built in. ui incommitchange be the foundingfounding check-inbranchfoundingaific ba<me<br><br>3.fossli<me Y clone clone http://wwwopenupdate/ol>
3 efossil; cd fossilsimpl/ol>
4 appeartion to give the branch a
5 specific ba<me<br><br>3.fossli in fossil4">6web-based GUI built in. ui "--bgco
6 /ol>
7 You cannot. All branches in fossil are public in the sense that
8 are all pushed and pulled together. There is no way to tell fossil
9 to only push or pull a subset of branches.
10
11 Of course, as long as you never push, you can make as many private
12 changes as you want.
M www/index.wiki
+6 -4
--- www/index.wiki
+++ www/index.wiki
@@ -13,11 +13,11 @@
1313
 [./build.wiki | compile it yourself].
1414
 Or you can grab
1515
 [http://www.fossil-scm.org/download.html | pre-compiled binaries].
1616
1717
18
-Feature Summary:
18
+<b>Feature Summary:</b>
1919
2020
 * Flexible workflow:<ul>
2121
 <li>Disconnected, distributed development like
2222
 <a href="http://kerneltrap.org/node/4982">git</a>,
2323
 <a href="http://www.monotone.ca/">monotone</a>,
@@ -51,12 +51,13 @@
5151
 on repository changes makes it exceedingly
5252
 unlikely that data will ever be lost because of a software bug.
5353
 * Ridiculously easy to [./build.wiki | install] and
5454
 [./quickstart.wiki | operate].
5555
56
-User Links:
56
+<b>User Links:</b>
5757
58
+ * [./faq.wiki | FAQ]
5859
 * The [./concepts.wiki | concepts] behind fossil
5960
 * [./build.wiki | Building And Installing]
6061
 * [./quickstart.wiki | Quick Start] guide to using fossil
6162
 * Fossil supports [./embeddeddoc.wiki | embedded documentation]
6263
 that is versioned along with project source code.
@@ -67,14 +68,15 @@
6768
 * Fossil contains a [./wikitheory.wiki | built-in wiki].
6869
 * There is a
6970
 [http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users | mailing list]
7071
 available for discussing fossil issues.
7172
 * [./qandc.wiki | Questions &amp; Criticisms] directed at fossil.
73
+ * [./reviews.wiki | Testimonials] from fossil users.
7274
 * Some (unfinished but expanding) extended
7375
 [./reference.wiki | reference documentation] for the fossil command line.
7476
75
-Developer Links:
77
+<b>Developer Links:</b>
7678
7779
 * [./pop.wiki | Principles Of Operation]
7880
 * The [./fileformat.wiki | file format] used by every content
7981
 file stored in the repository.
8082
 * The [./delta_format.wiki | format of deltas] used to
@@ -81,14 +83,14 @@
8183
 efficiently store changes between file revisions.
8284
 * The [./delta_encoder_algorithm.wiki | encoder algorithm] used to
8385
 efficiently generate deltas.
8486
 * The [./sync.wiki | synchronization protocol].
8587
86
-Competing Projects:
88
+<b>Competing Projects:</b>
8789
8890
 * [http://www.ditrack.org/ | DITrace] - A Distributed Issue Tracker
8991
 * [http://www.distract.wellquite.org/ | DisTract]
9092
 - Another distributed issue tracker based on
9193
 [http://www.monotone.ca/ | monotone].
9294
 * [http://www.monotone.ca/ | Monotone] - distributed
9395
 SCM in a single-file executable with a single-file SQLite
9496
 database repository.
9597
--- www/index.wiki
+++ www/index.wiki
@@ -13,11 +13,11 @@
13 [./build.wiki | compile it yourself].
14 Or you can grab
15 [http://www.fossil-scm.org/download.html | pre-compiled binaries].
16
17
18 Feature Summary:
19
20 * Flexible workflow:<ul>
21 <li>Disconnected, distributed development like
22 <a href="http://kerneltrap.org/node/4982">git</a>,
23 <a href="http://www.monotone.ca/">monotone</a>,
@@ -51,12 +51,13 @@
51 on repository changes makes it exceedingly
52 unlikely that data will ever be lost because of a software bug.
53 * Ridiculously easy to [./build.wiki | install] and
54 [./quickstart.wiki | operate].
55
56 User Links:
57
 
58 * The [./concepts.wiki | concepts] behind fossil
59 * [./build.wiki | Building And Installing]
60 * [./quickstart.wiki | Quick Start] guide to using fossil
61 * Fossil supports [./embeddeddoc.wiki | embedded documentation]
62 that is versioned along with project source code.
@@ -67,14 +68,15 @@
67 * Fossil contains a [./wikitheory.wiki | built-in wiki].
68 * There is a
69 [http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users | mailing list]
70 available for discussing fossil issues.
71 * [./qandc.wiki | Questions &amp; Criticisms] directed at fossil.
 
72 * Some (unfinished but expanding) extended
73 [./reference.wiki | reference documentation] for the fossil command line.
74
75 Developer Links:
76
77 * [./pop.wiki | Principles Of Operation]
78 * The [./fileformat.wiki | file format] used by every content
79 file stored in the repository.
80 * The [./delta_format.wiki | format of deltas] used to
@@ -81,14 +83,14 @@
81 efficiently store changes between file revisions.
82 * The [./delta_encoder_algorithm.wiki | encoder algorithm] used to
83 efficiently generate deltas.
84 * The [./sync.wiki | synchronization protocol].
85
86 Competing Projects:
87
88 * [http://www.ditrack.org/ | DITrace] - A Distributed Issue Tracker
89 * [http://www.distract.wellquite.org/ | DisTract]
90 - Another distributed issue tracker based on
91 [http://www.monotone.ca/ | monotone].
92 * [http://www.monotone.ca/ | Monotone] - distributed
93 SCM in a single-file executable with a single-file SQLite
94 database repository.
95
--- www/index.wiki
+++ www/index.wiki
@@ -13,11 +13,11 @@
13 [./build.wiki | compile it yourself].
14 Or you can grab
15 [http://www.fossil-scm.org/download.html | pre-compiled binaries].
16
17
18 <b>Feature Summary:</b>
19
20 * Flexible workflow:<ul>
21 <li>Disconnected, distributed development like
22 <a href="http://kerneltrap.org/node/4982">git</a>,
23 <a href="http://www.monotone.ca/">monotone</a>,
@@ -51,12 +51,13 @@
51 on repository changes makes it exceedingly
52 unlikely that data will ever be lost because of a software bug.
53 * Ridiculously easy to [./build.wiki | install] and
54 [./quickstart.wiki | operate].
55
56 <b>User Links:</b>
57
58 * [./faq.wiki | FAQ]
59 * The [./concepts.wiki | concepts] behind fossil
60 * [./build.wiki | Building And Installing]
61 * [./quickstart.wiki | Quick Start] guide to using fossil
62 * Fossil supports [./embeddeddoc.wiki | embedded documentation]
63 that is versioned along with project source code.
@@ -67,14 +68,15 @@
68 * Fossil contains a [./wikitheory.wiki | built-in wiki].
69 * There is a
70 [http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users | mailing list]
71 available for discussing fossil issues.
72 * [./qandc.wiki | Questions &amp; Criticisms] directed at fossil.
73 * [./reviews.wiki | Testimonials] from fossil users.
74 * Some (unfinished but expanding) extended
75 [./reference.wiki | reference documentation] for the fossil command line.
76
77 <b>Developer Links:</b>
78
79 * [./pop.wiki | Principles Of Operation]
80 * The [./fileformat.wiki | file format] used by every content
81 file stored in the repository.
82 * The [./delta_format.wiki | format of deltas] used to
@@ -81,14 +83,14 @@
83 efficiently store changes between file revisions.
84 * The [./delta_encoder_algorithm.wiki | encoder algorithm] used to
85 efficiently generate deltas.
86 * The [./sync.wiki | synchronization protocol].
87
88 <b>Competing Projects:</b>
89
90 * [http://www.ditrack.org/ | DITrace] - A Distributed Issue Tracker
91 * [http://www.distract.wellquite.org/ | DisTract]
92 - Another distributed issue tracker based on
93 [http://www.monotone.ca/ | monotone].
94 * [http://www.monotone.ca/ | Monotone] - distributed
95 SCM in a single-file executable with a single-file SQLite
96 database repository.
97
M www/qandc.wiki
+2
--- www/qandc.wiki
+++ www/qandc.wiki
@@ -1,10 +1,12 @@
11
 <nowiki>
22
 <h1 align="center">Questions And Criticisms</h1>
33
44
 <p>This page is a collection of real questions and criticisms that have been
55
 raised against fossil together with responses from the program's author.</p>
6
+
7
+<p>Note: See also the <a href="faq.wiki">Frequently Asked Questions</a>.</p>
68
79
 <b>Fossil sounds like a lot of reinvention of the wheel.
810
 Why create your own DVCS when you could have reused mercurial?</b>
911
1012
 <blockquote>
1113
1214
ADDED www/reviews.wiki
--- www/qandc.wiki
+++ www/qandc.wiki
@@ -1,10 +1,12 @@
1 <nowiki>
2 <h1 align="center">Questions And Criticisms</h1>
3
4 <p>This page is a collection of real questions and criticisms that have been
5 raised against fossil together with responses from the program's author.</p>
 
 
6
7 <b>Fossil sounds like a lot of reinvention of the wheel.
8 Why create your own DVCS when you could have reused mercurial?</b>
9
10 <blockquote>
11
12 DDED www/reviews.wiki
--- www/qandc.wiki
+++ www/qandc.wiki
@@ -1,10 +1,12 @@
1 <nowiki>
2 <h1 align="center">Questions And Criticisms</h1>
3
4 <p>This page is a collection of real questions and criticisms that have been
5 raised against fossil together with responses from the program's author.</p>
6
7 <p>Note: See also the <a href="faq.wiki">Frequently Asked Questions</a>.</p>
8
9 <b>Fossil sounds like a lot of reinvention of the wheel.
10 Why create your own DVCS when you could have reused mercurial?</b>
11
12 <blockquote>
13
14 DDED www/reviews.wiki
A www/reviews.wiki
+90
--- a/www/reviews.wiki
+++ b/www/reviews.wiki
@@ -0,0 +1,90 @@
1
+<h2 align="center">What People Athat it's the only version control I
2
+have found that I can get working through the VERY annoying MS
3
+firewalls at work.. (albeit through an ntlm proxy) and I just love
4
+sblockquote>
5
+
6
+
7
+<b>Joshua blockquote>
8
+With one of my several hats on, I'm in a small team using git. Another
9
+team member jun ntlm peoxy) and I just love
10
+sblockquote>
11
+
12
+
13
+<b>Joshua bl ockquote>
14
+With one of my several hats on, I'm in a small team using git. Another
15
+team member just checked some stuff into trunk that should have been on
16
+a branch. Nothing else had happened since, so in fossil I would have
17
+just edited that commit and put it on a new branch. In git that can't
18
+actually be done without danger once other people have pulled, so I had
19
+to create a new commit rolling back the changes, then branch and cherry
20
+pick the earlier changes, then figure out how to make my new branch
21
+shared instead of private. Just want to say thanks for fossil making my
22
+life easier on most of my projects, and being able to move commits to
23
+another branch after the fact and shared-by-default branches are good
24
+features. Also not having a misanthropic command line interface.
25
+</blockquote>
26
+<b>External links:<title>Rev1:</b>
27
+
28
+<div class="indent">
29
+Sometime in late 2007 I came across a link to fossil on
30
+<a href="http://www.fossil on <a
31
+href="https://sqli
32
+was a good thing I bookmarked it, because I
33
+link again (it to find the link again
34
+reasons I first hing). The reasons I firs
35
+sqlite project, d from the sqlite proj
36
+wrote JavaScript bindings for it:
37
+<a href="http://spiderape.sourceforge.net/plugins/sqlite/">
38
+http://spiderape.sourceforge.net/plugins/sqlite/<ine), and (B) it could run
39
+as a C
40
+practice CGI is the only way most hoste
41
+source repository with multiple user IDs.
42
+my only account password or SSH key for my
43
+much I trust the other developers, and non
44
+run standalone ser<title>Reviews</title>
45
+<b>External links:</b>
46
+
47
+ * [https://www.nixtu.info/2010/03/fossil-dvcs-on-go-first-impressions.html |
48
+ Fossil DVCS on the Go - First Impressions]
49
+
50
+<b>See Also:</b>
51
+
52
+ * [./quotes.wiki | Short Quotes on Fossil, Git, And DVCSes]
53
+
54
+<b>Daniel wblockquote6:</b>
55
+
56
+<div class="indent">
57
+The reasons I use fossil are that it's the only version control I
58
+have found that I can get working through the VERY annoying MS
59
+firewalls at work.. (albeit through an ntlm proxy) and I just love
60
+sblockquote>
61
+
62
+
63
+<b>Joshua blockquote>
64
+With one of my several hats on, I'm in a small team using git. Another
65
+team member just checked some stuff into trunk that should have been on
66
+a branch. Nothing else had happened since, so in fossil I would have
67
+just edited that commit and put it on a new branch. In git that can't
68
+actually be done without danger once other people have pulled, so I had
69
+to create a new commit rolling back the changes, then branch and cherry
70
+pick the earlier changes, then figure out how to make my new branch
71
+shared instead of private. Just want to say thanks for fossil making my
72
+life easier on most of my projects, and being able to move commits to
73
+another branch after the fact and shared-by-default branches are good
74
+features. Also not having a misanthropic command line interface.
75
+</blockquote>
76
+<b>External links:<title>Rev1:</b>
77
+
78
+<div class="indent">
79
+Sometime in late 2007 I came across a link to fossil on
80
+<a href="http://www.fossil on <a
81
+href="https://sqli
82
+was a good thing I bookmarked it, because I
83
+link again (it to find the link again
84
+reasons I first hing). The reasons I firs
85
+sqlite project, d from the sqlite proj
86
+wrote JavaScript bindings for it:
87
+<a href="http://spiderape.sourceforge.net/plugins/sqlite/">
88
+http://spiderape.sourceforge.net/plugins/sqlite/<ine), an[
89
+link again (it to find the link again
90
+reasons I fir
--- a/www/reviews.wiki
+++ b/www/reviews.wiki
@@ -0,0 +1,90 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
--- a/www/reviews.wiki
+++ b/www/reviews.wiki
@@ -0,0 +1,90 @@
1 <h2 align="center">What People Athat it's the only version control I
2 have found that I can get working through the VERY annoying MS
3 firewalls at work.. (albeit through an ntlm proxy) and I just love
4 sblockquote>
5
6
7 <b>Joshua blockquote>
8 With one of my several hats on, I'm in a small team using git. Another
9 team member jun ntlm peoxy) and I just love
10 sblockquote>
11
12
13 <b>Joshua bl ockquote>
14 With one of my several hats on, I'm in a small team using git. Another
15 team member just checked some stuff into trunk that should have been on
16 a branch. Nothing else had happened since, so in fossil I would have
17 just edited that commit and put it on a new branch. In git that can't
18 actually be done without danger once other people have pulled, so I had
19 to create a new commit rolling back the changes, then branch and cherry
20 pick the earlier changes, then figure out how to make my new branch
21 shared instead of private. Just want to say thanks for fossil making my
22 life easier on most of my projects, and being able to move commits to
23 another branch after the fact and shared-by-default branches are good
24 features. Also not having a misanthropic command line interface.
25 </blockquote>
26 <b>External links:<title>Rev1:</b>
27
28 <div class="indent">
29 Sometime in late 2007 I came across a link to fossil on
30 <a href="http://www.fossil on <a
31 href="https://sqli
32 was a good thing I bookmarked it, because I
33 link again (it to find the link again
34 reasons I first hing). The reasons I firs
35 sqlite project, d from the sqlite proj
36 wrote JavaScript bindings for it:
37 <a href="http://spiderape.sourceforge.net/plugins/sqlite/">
38 http://spiderape.sourceforge.net/plugins/sqlite/<ine), and (B) it could run
39 as a C
40 practice CGI is the only way most hoste
41 source repository with multiple user IDs.
42 my only account password or SSH key for my
43 much I trust the other developers, and non
44 run standalone ser<title>Reviews</title>
45 <b>External links:</b>
46
47 * [https://www.nixtu.info/2010/03/fossil-dvcs-on-go-first-impressions.html |
48 Fossil DVCS on the Go - First Impressions]
49
50 <b>See Also:</b>
51
52 * [./quotes.wiki | Short Quotes on Fossil, Git, And DVCSes]
53
54 <b>Daniel wblockquote6:</b>
55
56 <div class="indent">
57 The reasons I use fossil are that it's the only version control I
58 have found that I can get working through the VERY annoying MS
59 firewalls at work.. (albeit through an ntlm proxy) and I just love
60 sblockquote>
61
62
63 <b>Joshua blockquote>
64 With one of my several hats on, I'm in a small team using git. Another
65 team member just checked some stuff into trunk that should have been on
66 a branch. Nothing else had happened since, so in fossil I would have
67 just edited that commit and put it on a new branch. In git that can't
68 actually be done without danger once other people have pulled, so I had
69 to create a new commit rolling back the changes, then branch and cherry
70 pick the earlier changes, then figure out how to make my new branch
71 shared instead of private. Just want to say thanks for fossil making my
72 life easier on most of my projects, and being able to move commits to
73 another branch after the fact and shared-by-default branches are good
74 features. Also not having a misanthropic command line interface.
75 </blockquote>
76 <b>External links:<title>Rev1:</b>
77
78 <div class="indent">
79 Sometime in late 2007 I came across a link to fossil on
80 <a href="http://www.fossil on <a
81 href="https://sqli
82 was a good thing I bookmarked it, because I
83 link again (it to find the link again
84 reasons I first hing). The reasons I firs
85 sqlite project, d from the sqlite proj
86 wrote JavaScript bindings for it:
87 <a href="http://spiderape.sourceforge.net/plugins/sqlite/">
88 http://spiderape.sourceforge.net/plugins/sqlite/<ine), an[
89 link again (it to find the link again
90 reasons I fir

Keyboard Shortcuts

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