Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | use more utf-8 characters in the wiki, in stead of html entities |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
927d07c7273b32c9819ba3688554b6ad |
| User & Date: | jan.nijtmans 2012-08-31 09:03:44 |
Context
|
2012-08-31
| ||
| 12:44 | Merge the fork of trunk. (check-in: 231113ea user: mistachkin tags: trunk) | |
| 09:03 | use more utf-8 characters in the wiki, in stead of html entities (check-in: 927d07c7 user: jan.nijtmans tags: trunk) | |
| 08:58 | Removed some very old TODO comments (from me) which just clutter up the wiki help text. (check-in: f1c56bd3 user: stephan tags: trunk) | |
Changes
Changes to www/build.wiki.
81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 |
<b>./configure --help</b> </ol> <li><p>Run make to build the "fossil" or "fossil.exe" executable. The details depend on your platform and compiler. <ol type="a"> <li><p><i>Unix</i> → the configure-generated Makefile should work on all unix and unix-like systems. Simply type "<b>make</b>". <li><p><i>Unix without running "configure"</i> → if you prefer to avoid running configure, you can also use: <b>make -f Makefile.classic</b>. You may want to make minor edits to Makefile.classic to configure the build for your system. <li><p><i>MinGW/MinGW-w64</i> → Use the mingw makefile: "<b>make -f win/Makefile.mingw</b>". On a Windows box you will need either Cygwin or Msys as build environment. On Cygwin, Linux or Darwin you may want to make minor edits to win/Makefile.mingw to configure the cross-compile environment. <li><p><i>VC++</i> → Use the msc makefile. First change to the "win/" subdirectory ("<b>cd win</b>") then run "<b>nmake /f Makefile.msc</b>". </ol> </ol> <p>Note that Fossil requires the "zlib" compression library. This library is available by default on most unix systems, but it will typically have to |
| | | | |
81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 |
<b>./configure --help</b> </ol> <li><p>Run make to build the "fossil" or "fossil.exe" executable. The details depend on your platform and compiler. <ol type="a"> <li><p><i>Unix</i> → the configure-generated Makefile should work on all unix and unix-like systems. Simply type "<b>make</b>". <li><p><i>Unix without running "configure"</i> → if you prefer to avoid running configure, you can also use: <b>make -f Makefile.classic</b>. You may want to make minor edits to Makefile.classic to configure the build for your system. <li><p><i>MinGW/MinGW-w64</i> → Use the mingw makefile: "<b>make -f win/Makefile.mingw</b>". On a Windows box you will need either Cygwin or Msys as build environment. On Cygwin, Linux or Darwin you may want to make minor edits to win/Makefile.mingw to configure the cross-compile environment. <li><p><i>VC++</i> → Use the msc makefile. First change to the "win/" subdirectory ("<b>cd win</b>") then run "<b>nmake /f Makefile.msc</b>". </ol> </ol> <p>Note that Fossil requires the "zlib" compression library. This library is available by default on most unix systems, but it will typically have to |
Changes to www/checkin.wiki.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 |
<title>Check-in Checklist</title> <h2><u>Always</u> run the following checklist prior to <u>every</u> check-in or commit to the Fossil repository:</h2> Before every check-in: 0. <b>fossil user default</b> → your username is correct. 1. <b>fossil diff</b> → <ol type="a"> <li> No stray changes <li> All changes comply with the license <li> All inputs are scrubbed before use <li> No injection attacks via %s formats </ol> 2. <b>fossil extra</b> → no unmanaged files need to be added. 3. The check-in will go onto the desired branch. → Do <u>not</u> check into trunk without prior approval from the lead programmer (drh)! 4. auto-sync is on, or the system clock is verified 5. If sources files have been added or removed, ensure all makefiles and configure scripts have been updated accordingly. |
| | | | |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 |
<title>Check-in Checklist</title> <h2><u>Always</u> run the following checklist prior to <u>every</u> check-in or commit to the Fossil repository:</h2> Before every check-in: 0. <b>fossil user default</b> → your username is correct. 1. <b>fossil diff</b> → <ol type="a"> <li> No stray changes <li> All changes comply with the license <li> All inputs are scrubbed before use <li> No injection attacks via %s formats </ol> 2. <b>fossil extra</b> → no unmanaged files need to be added. 3. The check-in will go onto the desired branch. → Do <u>not</u> check into trunk without prior approval from the lead programmer (drh)! 4. auto-sync is on, or the system clock is verified 5. If sources files have been added or removed, ensure all makefiles and configure scripts have been updated accordingly. |
Changes to www/cmd_add.wiki.
15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 |
and [./cmd_clone.wiki | <code>clone</code>]
commands as very high-powered versions of the <code>add</code>
command that are combined with system level file movement and
networking functions. Not particularly accurate, but reasonable.
Typing <code> fossil add myfile</code> causes fossil to put
<i>myfile</i> into the repository at the next
<code>commit</code>—provided you issue it from within the source
tree, of course.
By contrast, <code> fossil add mydirectory</code> will add
<em><strong>all</strong></em> of the files in <i>mydirectory</i>, and
all of its sub-directories. In other words, adding a directory will
recursively add all of the directory's file system descendants to the
repository. This was an oft-requested feature, recently implemented.
|
| |
15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 |
and [./cmd_clone.wiki | <code>clone</code>]
commands as very high-powered versions of the <code>add</code>
command that are combined with system level file movement and
networking functions. Not particularly accurate, but reasonable.
Typing <code> fossil add myfile</code> causes fossil to put
<i>myfile</i> into the repository at the next
<code>commit</code>—provided you issue it from within the source
tree, of course.
By contrast, <code> fossil add mydirectory</code> will add
<em><strong>all</strong></em> of the files in <i>mydirectory</i>, and
all of its sub-directories. In other words, adding a directory will
recursively add all of the directory's file system descendants to the
repository. This was an oft-requested feature, recently implemented.
|
Changes to www/cmd_all.wiki.
36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 |
Or, you could just jog your memory.
The <code>all</code> command uses the <i>.fossil</i> file in the home
directory to find all of your repositories, so you can mess it up by
moving your repositories around. This is easy to do inadvertently if
you have a cavalier attitude about repos, but you'll know pretty
quickly that you've done it—many commands you try to use from
inside of a checkout won't work correctly. The <i>.fossil</i> file is
an <b>sqlite</b> db file which fossil uses to keeping track of
repository locations. Advice: if you move your repositories around,
let fossil know you did;
[./cmd_close.wiki | <code>close</code>] them before you move
them, and then [./cmd_open.wiki | <code>open</code>] them from
their new locations.
|
| |
36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 |
Or, you could just jog your memory.
The <code>all</code> command uses the <i>.fossil</i> file in the home
directory to find all of your repositories, so you can mess it up by
moving your repositories around. This is easy to do inadvertently if
you have a cavalier attitude about repos, but you'll know pretty
quickly that you've done it—many commands you try to use from
inside of a checkout won't work correctly. The <i>.fossil</i> file is
an <b>sqlite</b> db file which fossil uses to keeping track of
repository locations. Advice: if you move your repositories around,
let fossil know you did;
[./cmd_close.wiki | <code>close</code>] them before you move
them, and then [./cmd_open.wiki | <code>open</code>] them from
their new locations.
|
Changes to www/cmd_extra.wiki.
14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 |
in the repository before you do a commit. It will also tell you what
will be removed if you [./cmd_clean.wiki | <code>clean</code>]
the project.
Suppose, for example, you have a "noodle.src" file as a scratch pad
for source code, and you don't want to include your latest
hare-brained ideas in the repository? You don't <code>add</code> it
to the repository, of course—though there are ways you might add
it unintentionally. If your project is big, and you want to find
noodle.src, and anything else that isn't under source control within
the project directories, then<code> fossil extra </code> will
give you a list.
If you don't think this is all that useful, then you've never had to write
a shell script that only affects project files and leaves everything
|
| |
14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 |
in the repository before you do a commit. It will also tell you what
will be removed if you [./cmd_clean.wiki | <code>clean</code>]
the project.
Suppose, for example, you have a "noodle.src" file as a scratch pad
for source code, and you don't want to include your latest
hare-brained ideas in the repository? You don't <code>add</code> it
to the repository, of course—though there are ways you might add
it unintentionally. If your project is big, and you want to find
noodle.src, and anything else that isn't under source control within
the project directories, then<code> fossil extra </code> will
give you a list.
If you don't think this is all that useful, then you've never had to write
a shell script that only affects project files and leaves everything
|
Changes to www/cmd_status.wiki.
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 |
EDITED www/cmd_ls.wiki
EDITED www/cmd_update.wiki
EDITED www/index.wiki
$
</pre></nowiki>
Once I actually make changes to the repository (say, a
[./cmd_commit.wiki | commit]) most of that will change—all
of those files showing as "EDITED" will be checked in and won't
show up, and the artifact IDs will reflect the new state of the
repository.
If the only thing you want to see is which files in the checked-out
source tree have changed in some way, use the
[./cmd_changes.wiki | <code>changes</code>] command.
|
| |
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 |
EDITED www/cmd_ls.wiki
EDITED www/cmd_update.wiki
EDITED www/index.wiki
$
</pre></nowiki>
Once I actually make changes to the repository (say, a
[./cmd_commit.wiki | commit]) most of that will change—all
of those files showing as "EDITED" will be checked in and won't
show up, and the artifact IDs will reflect the new state of the
repository.
If the only thing you want to see is which files in the checked-out
source tree have changed in some way, use the
[./cmd_changes.wiki | <code>changes</code>] command.
|
Changes to www/inout.wiki.
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
..
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
Fossil has the ability to import and export repositories from and to [http://git-scm.com/ | Git]. And since most other version control systems will also import/export from Git, that means that you can import/export a Fossil repository to most version control systems using Git as an intermediary. <h2>Git → Fossil</h2> To import a Git repository into Fossil, run commands like this: <blockquote><pre> cd git-repo git fast-export --all | fossil import --git new-repo.fossil </pre></blockquote> ................................................................................ The --git option is not actually required. The git-fast-export file format is currently the only VCS interchange format that Fossil understands. But future versions of Fossil might be enhanced to understand other VCS interchange formats, and so for compatibility, use of the --git option is recommended. <h2>Fossil → Git</h2> To convert a Fossil repository into a Git repository, run commands like this: <blockquote><pre> git init new-repo cd new-repo |
|
|
|
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
..
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
Fossil has the ability to import and export repositories from and to [http://git-scm.com/ | Git]. And since most other version control systems will also import/export from Git, that means that you can import/export a Fossil repository to most version control systems using Git as an intermediary. <h2>Git → Fossil</h2> To import a Git repository into Fossil, run commands like this: <blockquote><pre> cd git-repo git fast-export --all | fossil import --git new-repo.fossil </pre></blockquote> ................................................................................ The --git option is not actually required. The git-fast-export file format is currently the only VCS interchange format that Fossil understands. But future versions of Fossil might be enhanced to understand other VCS interchange formats, and so for compatibility, use of the --git option is recommended. <h2>Fossil → Git</h2> To convert a Fossil repository into a Git repository, run commands like this: <blockquote><pre> git init new-repo cd new-repo |
Changes to www/mkindex.tcl.
58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 |
set n [llength $title]
lappend permindex [list $title $file]
for {set i 0} {$i<$n-1} {incr i} {
set prefix [lrange $title 0 $i]
set suffix [lrange $title [expr {$i+1}] end]
set firstword [string tolower [lindex $suffix 0]]
if {[lsearch $stopwords $firstword]<0} {
lappend permindex [list "$suffix — $prefix" $file]
}
}
}
set permindex [lsort -dict $permindex]
set out [open permutedindex.wiki w]
puts $out "<title>Permuted Index Of Fossil Documentation</title>"
puts $out "<nowiki>"
puts $out "<ul>"
foreach entry $permindex {
foreach {title file} $entry break
puts $out "<li><a href=\"$file\">$title</a></li>"
}
puts $out "</ul>"
|
| > |
58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 |
set n [llength $title]
lappend permindex [list $title $file]
for {set i 0} {$i<$n-1} {incr i} {
set prefix [lrange $title 0 $i]
set suffix [lrange $title [expr {$i+1}] end]
set firstword [string tolower [lindex $suffix 0]]
if {[lsearch $stopwords $firstword]<0} {
lappend permindex [list "$suffix \u2014 $prefix" $file]
}
}
}
set permindex [lsort -dict $permindex]
set out [open permutedindex.wiki w]
fconfigure $out -encoding utf-8 -translation lf
puts $out "<title>Permuted Index Of Fossil Documentation</title>"
puts $out "<nowiki>"
puts $out "<ul>"
foreach entry $permindex {
foreach {title file} $entry break
puts $out "<li><a href=\"$file\">$title</a></li>"
}
puts $out "</ul>"
|
Changes to www/permutedindex.wiki.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 |
<title>Permuted Index Of Fossil Documentation</title>
<nowiki>
<ul>
<li><a href="event.wiki">Events</a></li>
<li><a href="tech_overview.wiki">A Technical Overview Of The Design And Implementation
Of Fossil</a></li>
<li><a href="copyright-release.html">Agreement — Contributor License</a></li>
<li><a href="delta_encoder_algorithm.wiki">Algorithm — Fossil Delta Encoding</a></li>
<li><a href="faq.wiki">Asked Questions — Frequently</a></li>
<li><a href="password.wiki">Authentication — Password Management And</a></li>
<li><a href="private.wiki">Branches — Creating, Syncing, and Deleting Private</a></li>
<li><a href="branching.wiki">Branching, Forking, Merging, and Tagging</a></li>
<li><a href="bugtheory.wiki">Bug Tracking In Fossil</a></li>
<li><a href="makefile.wiki">Build Process — The Fossil</a></li>
<li><a href="build.wiki">Building and Installing Fossil</a></li>
<li><a href="changes.wiki">Changelog — Fossil</a></li>
<li><a href="checkin_names.wiki">Checkin And Version Names</a></li>
<li><a href="../test/release-checklist.wiki">Checklist — Pre-Release Testing</a></li>
<li><a href="foss-cklist.wiki">Checklist For Successful Open-Source Projects</a></li>
<li><a href="selfcheck.wiki">Checks — Fossil Repository Integrity Self</a></li>
<li><a href="contribute.wiki">Code or Documentation To The Fossil Project — Contributing</a></li>
<li><a href="style.wiki">Code Style Guidelines — Source</a></li>
<li><a href="concepts.wiki">Concepts — Fossil Core</a></li>
<li><a href="server.wiki">Configure A Fossil Server — How To</a></li>
<li><a href="shunning.wiki">Content From Fossil — Shunning: Deleting</a></li>
<li><a href="contribute.wiki">Contributing Code or Documentation To The Fossil Project</a></li>
<li><a href="copyright-release.html">Contributor License Agreement</a></li>
<li><a href="concepts.wiki">Core Concepts — Fossil</a></li>
<li><a href="private.wiki">Creating, Syncing, and Deleting Private Branches</a></li>
<li><a href="qandc.wiki">Criticisms — Questions And</a></li>
<li><a href="custom_ticket.wiki">Customizing The Ticket System</a></li>
<li><a href="tech_overview.wiki">Databases Used By Fossil — SQLite</a></li>
<li><a href="shunning.wiki">Deleting Content From Fossil — Shunning:</a></li>
<li><a href="private.wiki">Deleting Private Branches — Creating, Syncing, and</a></li>
<li><a href="delta_encoder_algorithm.wiki">Delta Encoding Algorithm — Fossil</a></li>
<li><a href="delta_format.wiki">Delta Format — Fossil</a></li>
<li><a href="tech_overview.wiki">Design And Implementation Of Fossil — A Technical Overview Of The</a></li>
<li><a href="theory1.wiki">Design Of The Fossil DVCS — Thoughts On The</a></li>
<li><a href="embeddeddoc.wiki">Documentation — Embedded Project</a></li>
<li><a href="contribute.wiki">Documentation To The Fossil Project — Contributing Code or</a></li>
<li><a href="theory1.wiki">DVCS — Thoughts On The Design Of The Fossil</a></li>
<li><a href="quotes.wiki">DVCSes in General — Quotes: What People Are Saying About Fossil, Git, and</a></li>
<li><a href="embeddeddoc.wiki">Embedded Project Documentation</a></li>
<li><a href="delta_encoder_algorithm.wiki">Encoding Algorithm — Fossil Delta</a></li>
<li><a href="inout.wiki">Export To And From Git — Import And</a></li>
<li><a href="fileformat.wiki">File Format — Fossil</a></li>
<li><a href="branching.wiki">Forking, Merging, and Tagging — Branching,</a></li>
<li><a href="delta_format.wiki">Format — Fossil Delta</a></li>
<li><a href="fileformat.wiki">Format — Fossil File</a></li>
<li><a href="changes.wiki">Fossil Changelog</a></li>
<li><a href="concepts.wiki">Fossil Core Concepts</a></li>
<li><a href="delta_encoder_algorithm.wiki">Fossil Delta Encoding Algorithm</a></li>
<li><a href="delta_format.wiki">Fossil Delta Format</a></li>
<li><a href="fileformat.wiki">Fossil File Format</a></li>
<li><a href="quickstart.wiki">Fossil Quick Start Guide</a></li>
<li><a href="selfcheck.wiki">Fossil Repository Integrity Self Checks</a></li>
<li><a href="selfhost.wiki">Fossil Self Hosting Repositories</a></li>
<li><a href="settings.wiki">Fossil Settings</a></li>
<li><a href="fossil-v-git.wiki">Fossil Versus Git</a></li>
<li><a href="quotes.wiki">Fossil, Git, and DVCSes in General — Quotes: What People Are Saying About</a></li>
<li><a href="faq.wiki">Frequently Asked Questions</a></li>
<li><a href="shunning.wiki">From Fossil — Shunning: Deleting Content</a></li>
<li><a href="inout.wiki">From Git — Import And Export To And</a></li>
<li><a href="quotes.wiki">General — Quotes: What People Are Saying About Fossil, Git, and DVCSes in</a></li>
<li><a href="fossil-v-git.wiki">Git — Fossil Versus</a></li>
<li><a href="inout.wiki">Git — Import And Export To And From</a></li>
<li><a href="quotes.wiki">Git, and DVCSes in General — Quotes: What People Are Saying About Fossil,</a></li>
<li><a href="quickstart.wiki">Guide — Fossil Quick Start</a></li>
<li><a href="style.wiki">Guidelines — Source Code Style</a></li>
<li><a href="index.wiki">Home Page</a></li>
<li><a href="selfhost.wiki">Hosting Repositories — Fossil Self</a></li>
<li><a href="server.wiki">How To Configure A Fossil Server</a></li>
<li><a href="tech_overview.wiki">Implementation Of Fossil — A Technical Overview Of The Design And</a></li>
<li><a href="inout.wiki">Import And Export To And From Git</a></li>
<li><a href="build.wiki">Installing Fossil — Building and</a></li>
<li><a href="selfcheck.wiki">Integrity Self Checks — Fossil Repository</a></li>
<li><a href="webui.wiki">Interface — The Fossil Web</a></li>
<li><a href="copyright-release.html">License Agreement — Contributor</a></li>
<li><a href="password.wiki">Management And Authentication — Password</a></li>
<li><a href="branching.wiki">Merging, and Tagging — Branching, Forking,</a></li>
<li><a href="checkin_names.wiki">Names — Checkin And Version</a></li>
<li><a href="foss-cklist.wiki">Open-Source Projects — Checklist For Successful</a></li>
<li><a href="pop.wiki">Operations — Principles Of</a></li>
<li><a href="tech_overview.wiki">Overview Of The Design And Implementation Of Fossil — A Technical</a></li>
<li><a href="index.wiki">Page — Home</a></li>
<li><a href="password.wiki">Password Management And Authentication</a></li>
<li><a href="quotes.wiki">People Are Saying About Fossil, Git, and DVCSes in General — Quotes: What</a></li>
<li><a href="stats.wiki">Performance Statistics</a></li>
<li><a href="../test/release-checklist.wiki">Pre-Release Testing Checklist</a></li>
<li><a href="pop.wiki">Principles Of Operations</a></li>
<li><a href="private.wiki">Private Branches — Creating, Syncing, and Deleting</a></li>
<li><a href="makefile.wiki">Process — The Fossil Build</a></li>
<li><a href="contribute.wiki">Project — Contributing Code or Documentation To The Fossil</a></li>
<li><a href="embeddeddoc.wiki">Project Documentation — Embedded</a></li>
<li><a href="foss-cklist.wiki">Projects — Checklist For Successful Open-Source</a></li>
<li><a href="sync.wiki">Protocol — The Fossil Sync</a></li>
<li><a href="faq.wiki">Questions — Frequently Asked</a></li>
<li><a href="qandc.wiki">Questions And Criticisms</a></li>
<li><a href="quickstart.wiki">Quick Start Guide — Fossil</a></li>
<li><a href="quotes.wiki">Quotes: What People Are Saying About Fossil, Git, and DVCSes in General</a></li>
<li><a href="selfhost.wiki">Repositories — Fossil Self Hosting</a></li>
<li><a href="selfcheck.wiki">Repository Integrity Self Checks — Fossil</a></li>
<li><a href="quotes.wiki">Saying About Fossil, Git, and DVCSes in General — Quotes: What People Are</a></li>
<li><a href="selfcheck.wiki">Self Checks — Fossil Repository Integrity</a></li>
<li><a href="selfhost.wiki">Self Hosting Repositories — Fossil</a></li>
<li><a href="server.wiki">Server — How To Configure A Fossil</a></li>
<li><a href="settings.wiki">Settings — Fossil</a></li>
<li><a href="shunning.wiki">Shunning: Deleting Content From Fossil</a></li>
<li><a href="style.wiki">Source Code Style Guidelines</a></li>
<li><a href="tech_overview.wiki">SQLite Databases Used By Fossil</a></li>
<li><a href="ssl.wiki">SSL with Fossil — Using</a></li>
<li><a href="quickstart.wiki">Start Guide — Fossil Quick</a></li>
<li><a href="stats.wiki">Statistics — Performance</a></li>
<li><a href="style.wiki">Style Guidelines — Source Code</a></li>
<li><a href="foss-cklist.wiki">Successful Open-Source Projects — Checklist For</a></li>
<li><a href="sync.wiki">Sync Protocol — The Fossil</a></li>
<li><a href="private.wiki">Syncing, and Deleting Private Branches — Creating,</a></li>
<li><a href="custom_ticket.wiki">System — Customizing The Ticket</a></li>
<li><a href="branching.wiki">Tagging — Branching, Forking, Merging, and</a></li>
<li><a href="tech_overview.wiki">Technical Overview Of The Design And Implementation Of Fossil — A</a></li>
<li><a href="../test/release-checklist.wiki">Testing Checklist — Pre-Release</a></li>
<li><a href="makefile.wiki">The Fossil Build Process</a></li>
<li><a href="sync.wiki">The Fossil Sync Protocol</a></li>
<li><a href="webui.wiki">The Fossil Web Interface</a></li>
<li><a href="theory1.wiki">Thoughts On The Design Of The Fossil DVCS</a></li>
<li><a href="custom_ticket.wiki">Ticket System — Customizing The</a></li>
<li><a href="bugtheory.wiki">Tracking In Fossil — Bug</a></li>
<li><a href="ssl.wiki">Using SSL with Fossil</a></li>
<li><a href="checkin_names.wiki">Version Names — Checkin And</a></li>
<li><a href="fossil-v-git.wiki">Versus Git — Fossil</a></li>
<li><a href="webui.wiki">Web Interface — The Fossil</a></li>
<li><a href="quotes.wiki">What People Are Saying About Fossil, Git, and DVCSes in General — Quotes:</a></li>
<li><a href="wikitheory.wiki">Wiki In Fossil</a></li>
<li><a href="ssl.wiki">with Fossil — Using SSL</a></li>
</ul>
|
| | | | | | | < > | | | | | | | | | | | | | | | < | > | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | < | > | | < > | | | | | | | | | | | | | | | | | | | | | | | | | | |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 |
<title>Permuted Index Of Fossil Documentation</title>
<nowiki>
<ul>
<li><a href="event.wiki">Events</a></li>
<li><a href="tech_overview.wiki">A Technical Overview Of The Design And Implementation
Of Fossil</a></li>
<li><a href="copyright-release.html">Agreement — Contributor License</a></li>
<li><a href="delta_encoder_algorithm.wiki">Algorithm — Fossil Delta Encoding</a></li>
<li><a href="faq.wiki">Asked Questions — Frequently</a></li>
<li><a href="password.wiki">Authentication — Password Management And</a></li>
<li><a href="private.wiki">Branches — Creating, Syncing, and Deleting Private</a></li>
<li><a href="branching.wiki">Branching, Forking, Merging, and Tagging</a></li>
<li><a href="bugtheory.wiki">Bug Tracking In Fossil</a></li>
<li><a href="makefile.wiki">Build Process — The Fossil</a></li>
<li><a href="build.wiki">Building and Installing Fossil</a></li>
<li><a href="changes.wiki">Changelog — Fossil</a></li>
<li><a href="checkin_names.wiki">Checkin And Version Names</a></li>
<li><a href="foss-cklist.wiki">Checklist For Successful Open-Source Projects</a></li>
<li><a href="../test/release-checklist.wiki">Checklist — Pre-Release Testing</a></li>
<li><a href="selfcheck.wiki">Checks — Fossil Repository Integrity Self</a></li>
<li><a href="contribute.wiki">Code or Documentation To The Fossil Project — Contributing</a></li>
<li><a href="style.wiki">Code Style Guidelines — Source</a></li>
<li><a href="concepts.wiki">Concepts — Fossil Core</a></li>
<li><a href="server.wiki">Configure A Fossil Server — How To</a></li>
<li><a href="shunning.wiki">Content From Fossil — Shunning: Deleting</a></li>
<li><a href="contribute.wiki">Contributing Code or Documentation To The Fossil Project</a></li>
<li><a href="copyright-release.html">Contributor License Agreement</a></li>
<li><a href="concepts.wiki">Core Concepts — Fossil</a></li>
<li><a href="private.wiki">Creating, Syncing, and Deleting Private Branches</a></li>
<li><a href="qandc.wiki">Criticisms — Questions And</a></li>
<li><a href="custom_ticket.wiki">Customizing The Ticket System</a></li>
<li><a href="tech_overview.wiki">Databases Used By Fossil — SQLite</a></li>
<li><a href="shunning.wiki">Deleting Content From Fossil — Shunning:</a></li>
<li><a href="private.wiki">Deleting Private Branches — Creating, Syncing, and</a></li>
<li><a href="delta_encoder_algorithm.wiki">Delta Encoding Algorithm — Fossil</a></li>
<li><a href="delta_format.wiki">Delta Format — Fossil</a></li>
<li><a href="tech_overview.wiki">Design And Implementation Of Fossil — A Technical Overview Of The</a></li>
<li><a href="theory1.wiki">Design Of The Fossil DVCS — Thoughts On The</a></li>
<li><a href="contribute.wiki">Documentation To The Fossil Project — Contributing Code or</a></li>
<li><a href="embeddeddoc.wiki">Documentation — Embedded Project</a></li>
<li><a href="theory1.wiki">DVCS — Thoughts On The Design Of The Fossil</a></li>
<li><a href="quotes.wiki">DVCSes in General — Quotes: What People Are Saying About Fossil, Git, and</a></li>
<li><a href="embeddeddoc.wiki">Embedded Project Documentation</a></li>
<li><a href="delta_encoder_algorithm.wiki">Encoding Algorithm — Fossil Delta</a></li>
<li><a href="inout.wiki">Export To And From Git — Import And</a></li>
<li><a href="fileformat.wiki">File Format — Fossil</a></li>
<li><a href="branching.wiki">Forking, Merging, and Tagging — Branching,</a></li>
<li><a href="delta_format.wiki">Format — Fossil Delta</a></li>
<li><a href="fileformat.wiki">Format — Fossil File</a></li>
<li><a href="changes.wiki">Fossil Changelog</a></li>
<li><a href="concepts.wiki">Fossil Core Concepts</a></li>
<li><a href="delta_encoder_algorithm.wiki">Fossil Delta Encoding Algorithm</a></li>
<li><a href="delta_format.wiki">Fossil Delta Format</a></li>
<li><a href="fileformat.wiki">Fossil File Format</a></li>
<li><a href="quickstart.wiki">Fossil Quick Start Guide</a></li>
<li><a href="selfcheck.wiki">Fossil Repository Integrity Self Checks</a></li>
<li><a href="selfhost.wiki">Fossil Self Hosting Repositories</a></li>
<li><a href="settings.wiki">Fossil Settings</a></li>
<li><a href="fossil-v-git.wiki">Fossil Versus Git</a></li>
<li><a href="quotes.wiki">Fossil, Git, and DVCSes in General — Quotes: What People Are Saying About</a></li>
<li><a href="faq.wiki">Frequently Asked Questions</a></li>
<li><a href="shunning.wiki">From Fossil — Shunning: Deleting Content</a></li>
<li><a href="inout.wiki">From Git — Import And Export To And</a></li>
<li><a href="quotes.wiki">General — Quotes: What People Are Saying About Fossil, Git, and DVCSes in</a></li>
<li><a href="fossil-v-git.wiki">Git — Fossil Versus</a></li>
<li><a href="inout.wiki">Git — Import And Export To And From</a></li>
<li><a href="quotes.wiki">Git, and DVCSes in General — Quotes: What People Are Saying About Fossil,</a></li>
<li><a href="quickstart.wiki">Guide — Fossil Quick Start</a></li>
<li><a href="style.wiki">Guidelines — Source Code Style</a></li>
<li><a href="index.wiki">Home Page</a></li>
<li><a href="selfhost.wiki">Hosting Repositories — Fossil Self</a></li>
<li><a href="server.wiki">How To Configure A Fossil Server</a></li>
<li><a href="tech_overview.wiki">Implementation Of Fossil — A Technical Overview Of The Design And</a></li>
<li><a href="inout.wiki">Import And Export To And From Git</a></li>
<li><a href="build.wiki">Installing Fossil — Building and</a></li>
<li><a href="selfcheck.wiki">Integrity Self Checks — Fossil Repository</a></li>
<li><a href="webui.wiki">Interface — The Fossil Web</a></li>
<li><a href="copyright-release.html">License Agreement — Contributor</a></li>
<li><a href="password.wiki">Management And Authentication — Password</a></li>
<li><a href="branching.wiki">Merging, and Tagging — Branching, Forking,</a></li>
<li><a href="checkin_names.wiki">Names — Checkin And Version</a></li>
<li><a href="foss-cklist.wiki">Open-Source Projects — Checklist For Successful</a></li>
<li><a href="pop.wiki">Operations — Principles Of</a></li>
<li><a href="tech_overview.wiki">Overview Of The Design And Implementation Of Fossil — A Technical</a></li>
<li><a href="index.wiki">Page — Home</a></li>
<li><a href="password.wiki">Password Management And Authentication</a></li>
<li><a href="quotes.wiki">People Are Saying About Fossil, Git, and DVCSes in General — Quotes: What</a></li>
<li><a href="stats.wiki">Performance Statistics</a></li>
<li><a href="../test/release-checklist.wiki">Pre-Release Testing Checklist</a></li>
<li><a href="pop.wiki">Principles Of Operations</a></li>
<li><a href="private.wiki">Private Branches — Creating, Syncing, and Deleting</a></li>
<li><a href="makefile.wiki">Process — The Fossil Build</a></li>
<li><a href="embeddeddoc.wiki">Project Documentation — Embedded</a></li>
<li><a href="contribute.wiki">Project — Contributing Code or Documentation To The Fossil</a></li>
<li><a href="foss-cklist.wiki">Projects — Checklist For Successful Open-Source</a></li>
<li><a href="sync.wiki">Protocol — The Fossil Sync</a></li>
<li><a href="qandc.wiki">Questions And Criticisms</a></li>
<li><a href="faq.wiki">Questions — Frequently Asked</a></li>
<li><a href="quickstart.wiki">Quick Start Guide — Fossil</a></li>
<li><a href="quotes.wiki">Quotes: What People Are Saying About Fossil, Git, and DVCSes in General</a></li>
<li><a href="selfhost.wiki">Repositories — Fossil Self Hosting</a></li>
<li><a href="selfcheck.wiki">Repository Integrity Self Checks — Fossil</a></li>
<li><a href="quotes.wiki">Saying About Fossil, Git, and DVCSes in General — Quotes: What People Are</a></li>
<li><a href="selfcheck.wiki">Self Checks — Fossil Repository Integrity</a></li>
<li><a href="selfhost.wiki">Self Hosting Repositories — Fossil</a></li>
<li><a href="server.wiki">Server — How To Configure A Fossil</a></li>
<li><a href="settings.wiki">Settings — Fossil</a></li>
<li><a href="shunning.wiki">Shunning: Deleting Content From Fossil</a></li>
<li><a href="style.wiki">Source Code Style Guidelines</a></li>
<li><a href="tech_overview.wiki">SQLite Databases Used By Fossil</a></li>
<li><a href="ssl.wiki">SSL with Fossil — Using</a></li>
<li><a href="quickstart.wiki">Start Guide — Fossil Quick</a></li>
<li><a href="stats.wiki">Statistics — Performance</a></li>
<li><a href="style.wiki">Style Guidelines — Source Code</a></li>
<li><a href="foss-cklist.wiki">Successful Open-Source Projects — Checklist For</a></li>
<li><a href="sync.wiki">Sync Protocol — The Fossil</a></li>
<li><a href="private.wiki">Syncing, and Deleting Private Branches — Creating,</a></li>
<li><a href="custom_ticket.wiki">System — Customizing The Ticket</a></li>
<li><a href="branching.wiki">Tagging — Branching, Forking, Merging, and</a></li>
<li><a href="tech_overview.wiki">Technical Overview Of The Design And Implementation Of Fossil — A</a></li>
<li><a href="../test/release-checklist.wiki">Testing Checklist — Pre-Release</a></li>
<li><a href="makefile.wiki">The Fossil Build Process</a></li>
<li><a href="sync.wiki">The Fossil Sync Protocol</a></li>
<li><a href="webui.wiki">The Fossil Web Interface</a></li>
<li><a href="theory1.wiki">Thoughts On The Design Of The Fossil DVCS</a></li>
<li><a href="custom_ticket.wiki">Ticket System — Customizing The</a></li>
<li><a href="bugtheory.wiki">Tracking In Fossil — Bug</a></li>
<li><a href="ssl.wiki">Using SSL with Fossil</a></li>
<li><a href="checkin_names.wiki">Version Names — Checkin And</a></li>
<li><a href="fossil-v-git.wiki">Versus Git — Fossil</a></li>
<li><a href="webui.wiki">Web Interface — The Fossil</a></li>
<li><a href="quotes.wiki">What People Are Saying About Fossil, Git, and DVCSes in General — Quotes:</a></li>
<li><a href="wikitheory.wiki">Wiki In Fossil</a></li>
<li><a href="ssl.wiki">with Fossil — Using SSL</a></li>
</ul>
|
Changes to www/reference.wiki.
1 2 3 4 5 6 7 8 9 10 11 12 .. 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 .. 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 ... 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 ... 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 ... 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 ... 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 ... 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 ... 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 ... 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 ... 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 ... 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 ... 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 ... 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 ... 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 |
<h2>Command Line Interface Reference</h2> This is an easy introduction to the fossil command line interface (cli). It assumes some familiarity with using the command line, and with Source Code Maintenence (SCM) systems—but not <i>too</i> much. If you are trying to find information about fossil's web capabilities, see the <a href="index.wiki">Fossil Home</a> and <a href="wikitheory.wiki">Fossil Wiki</a> pages for pointers. <h3>Things to note</h3> ................................................................................ '-' (hyphen, or dash) character. This is very similar to Tcl. Think of fossil as a shell you invoke and feed a command to, including any options, and it will make more sense. * Any fossil command is acceptable once enough of it has been entered to make the intent unambiguous. 'clo' is a proper prefix of both the 'clone' and 'close' commands, for instance, but 'clon' is enough to make the intent—the 'clone' command—unambiguous. * Pragmatically, a [./concepts.wiki#keyconc | <u>version</u>] in <b>fossil</b> is a 40-character long string of hexadecimal. <b>fossil</b> will be able to figure out which version you want with any <i>distinct</i> prefix of that string which is at least four characters long. <em>Commands which require a version are looking for the string, a distinct prefix of the ................................................................................ understand if you can run a repository, watch it in a browser, and hack around with it in a simplified environment (your tests) with guaranteed and fast access to the sources & docs (your cloned fossil repository). <br /><br /> <br /> <b>You should</b> probably start interacting with fossil at the command line by asking it what it can do: <a name="tof">ˆ</a> <code>$ fossil help</code><nowiki><pre> Usage: fossil help COMMAND. Available COMMANDs:</pre><table width="80%" style="font-family: fixed, courier, monospace;"> <tr> <td><a href="#add">add</a>*</td> ................................................................................ </pre> <b>What follows</b> is a survey of what you get if you type<code> fossil help <i>command</i> </code>for all of the commands listed above. There are links to individual pages for each of them; pages with content (commands marked with a '*' are done) go into the reason for a command in a bit more depth than the program help. <pre> <hr><a href="#tof">ˆ</a> <a name="add">Usage: </a><code><a href="cmd_add.wiki">fossil add</a></code> FILE... Make arrangements to add one or more files to the current checkout at the next commit. <hr><a href="#tof">ˆ</a> <a name="all">Usage: </a><code><a href="cmd_all.wiki">fossil all</a></code> (list|pull|push|rebuild|sync) The ~/.fossil file records the location of all repositories for a user. This command performs certain operations on all repositories that can be useful before or after a period of disconnection operation. On Win32 systems, this file is located in %LOCALAPPDATA%, %APDDATA% or %HOMEPATH% and is named _fossil. ................................................................................ sync Run a "sync" on all repositories Respositories are automatically added to the set of known repositories when one of the following commands against the repository: clone, info, pull, push, or sync <hr><a href="#tof">ˆ</a> <a name="branch">Usage: </a><code><a href="cmd_branch.wiki">fossil branch</a></code> SUBCOMMAND ... ?-R|--repository FILE? Run various subcommands on the branches of the open repository or of the repository identified by the -R or --repository option. fossil branch new BRANCH-NAME BASIS ?-bgcolor COLOR? ................................................................................ Create a new branch BRANCH-NAME off of check-in BASIS. You can optionally give the branch a default color. fossil branch list List all branches <hr><a href="#tof">ˆ</a> <a name="cgi">Usage: </a><a href="cmd_cgi.wiki">fossil cgi</a> SCRIPT The SCRIPT argument is the name of a file that is the CGI script that is being run. The command name, "cgi", may be omitted if the GATEWAY_INTERFACE environment variable is set to "CGI" (which should always be the case for CGI scripts run by a webserver.) The SCRIPT file should look something like this: ................................................................................ #!/usr/bin/fossil repository: /home/somebody/project.db The second line defines the name of the repository. After locating the repository, fossil will generate a webpage on stdout based on the values of standard CGI environment variables. <hr><a href="#tof">ˆ</a> <a name="changes">Usage: </a><a href="cmd_changes.wiki">fossil changes</a> Report on the edit status of all files in the current checkout. See also the "status" and "extra" commands. <hr><a href="#tof">ˆ</a> <a name="checkout">Usage: </a><a href="cmd_checkout.wiki">fossil checkout</a> VERSION ?-f|--force? Check out a version specified on the command-line. This command will not overwrite edited files in the current checkout unless the --force option appears on the command-line. See also the "update" command. <hr><a href="#tof">ˆ</a> <a name="commit">Usage: </a><a href="cmd_commit.wiki">fossil commit</a> ?-m COMMENT? ?--nosign? ?FILE...? fossil ci ... (as above) Create a new version containing all of the changes in the current checkout. You will be prompted to enter a check-in comment unless the "-m" option is used to specify a comment line. You will be prompted for your GPG passphrase in order to sign the new manifest unless the "--nosign" option is used. All files that have changed will be committed unless some subset of files is specified on the command line. <hr><a href="#tof">ˆ</a> <a name="clean">Usage: </a><a href="cmd_clean.wiki">fossil clean</a> ?-all? Delete all "extra" files in the source tree. "Extra" files are files that are not officially part of the checkout. See also the "extra" command. This operation cannot be undone. You will be prompted before removing each file. If you are sure you wish to remove all "extra" files you can specify the optional -all flag. <hr><a href="#tof">ˆ</a> <a name="clone">Usage: </a><a href="cmd_clone.wiki">fossil clone</a> URL FILENAME Make a clone of a repository specified by URL in the local file named FILENAME. <hr><a href="#tof">ˆ</a> <a name="close">Usage: </a><a href="cmd_close.wiki">fossil close</a> ?-f|--force? The opposite of "open". Close the current database connection. Require a -f or --force flag if there are unsaved changed in the current check-out. <hr><a href="#tof">ˆ</a> <a name="configuration">Usage: </a><a href="cmd_configure.wiki">fossil configuration</a> METHOD ... Where METHOD is one of: export import merge pull push reset. All methods accept the -R or --repository option to specific a repository. fossil configuration export AREA FILENAME Write to FILENAME exported configuraton information for AREA. ................................................................................ Restore the configuration to the default. AREA as above. WARNING: Do not import, merge, or pull configurations from an untrusted source. The inbound configuration is not checked for safety and can introduce security vulnerabilities. <hr><a href="#tof">ˆ</a> COMMAND: deconstruct <a name="deconstruct">Usage: </a><a href="cmd_deconstruct.wiki">fossil deconstruct</a> ?-R|--repository REPOSITORY? DESTINATION Populates the indicated DESTINATION directory with copies of all artifcats contained within the repository. Artifacts are named AA/bbbbb where AA is the first 2 characters of the artifact ID and bbbbb is the remaining 38 characters. <hr><a href="#tof">ˆ</a> <a name="rm">Usage: </a><a href="cmd_rm.wiki">fossil rm</a> FILE... or: fossil del FILE... Remove one or more files from the tree. <hr><a href="#tof">ˆ</a> <a name="descendants">Usage: </a><a href="cmd_descendants.wiki">fossil descendants</a> ?CHECKIN-ID? Find all leaf descendants of the check-in specified or if the argument is omitted, of the check-in currently checked out. <hr><a href="#tof">ˆ</a> <a name="diff">Usage: </a><a href="cmd_diff.wiki">fossil diff</a>|gdiff ?-i? ?-r REVISION? FILE... Show the difference between the current version of a file (as it exists on disk) and that same file as it was checked out. diff will show a textual diff while gdiff will attempt to run a graphical diff command that you have setup. If the choosen command is not yet configured, the internal textual diff command will be ................................................................................ fossil setting gdiff-command tkdiff fossil setting gdiff-command eskill22 fossil setting gdiff-command tortoisemerge fossil setting gdiff-command meld fossil setting gdiff-command xxdiff fossil setting gdiff-command kdiff3 <hr><a href="#tof">ˆ</a> <a name="extra">Usage: </a><a href="cmd_extra.wiki">fossil extra</a> Print a list of all files in the source tree that are not part of the current checkout. See also the "clean" command. <hr><a href="#tof">ˆ</a> <a name="help">Usage: </a><a href="cmd_help.wiki">fossil help</a> COMMAND Display information on how to use COMMAND <hr><a href="#tof">ˆ</a> <a name="http">Usage: </a><a href="cmd_http.wiki">fossil http</a> REPOSITORY Handle a single HTTP request appearing on stdin. The resulting webpage is delivered on stdout. This method is used to launch an HTTP request handler from inetd, for example. The argument is the name of the repository. <hr><a href="#tof">ˆ</a> <a name="info">Usage: </a><a href="cmd_info.wiki">fossil info</a> ?ARTIFACT-ID|FILENAME? With no arguments, provide information about the current tree. If an argument is specified, provide information about the object in the respository of the current tree that the argument refers to. Or if the argument is the name of a repository, show information about that repository. <hr><a href="#tof">ˆ</a> <a name="leaves">Usage: </a><a href="cmd_leaves.wiki">fossil leaves</a> Find leaves of all branches. <hr><a href="#tof">ˆ</a> <a name="ls">Usage: </a><a href="cmd_ls.wiki">fossil ls</a> Show the names of all files in the current checkout <hr><a href="#tof">ˆ</a> <a name="merge">Usage: </a><a href="cmd_merge.wiki">fossil merge</a> VERSION The argument is a version that should be merged into the current checkout. Only file content is merged. The result continues to use the file and directory names from the current check-out even if those names might have been changed in the branch being merged in. <hr><a href="#tof">ˆ</a> <a name="mv">Usage: </a><a href="cmd_mv.wiki">fossil mv|rename</a> OLDNAME NEWNAME or: fossil mv|rename OLDNAME... DIR Move or rename one or more files within the tree This command does not rename the files on disk. All this command does is record the fact that filenames have changed so that appropriate notations can be made at the next commit/checkin. <hr><a href="#tof">ˆ</a> <a name="new">Usage: </a><a href="cmd_new.wiki">fossil new</a> FILENAME Create a repository for a new project in the file named FILENAME. This command is distinct from "clone". The "clone" command makes a copy of an existing project. This command starts a new project. <hr><a href="#tof">ˆ</a> <a name="open">Usage: </a><a href="cmd_open.wiki">fossil open</a> FILENAME Open a connection to the local repository in FILENAME. A checkout for the repository is created with its root at the working directory. See also the "close" command. <hr><a href="#tof">ˆ</a> <a name="rstats">Usage: </a><a href="cmd_rstats.wiki">fossil rstats</a> Deliver a report of the repository statistics for the current checkout. <hr><a href="#tof">ˆ</a> <a name="pull">Usage: </a><a href="cmd_pull.wiki">fossil pull</a> ?URL? ?-R|--respository REPOSITORY? Pull changes in a remote repository into the local repository. The repository is identified by the -R or --repository option. If there is no such option then the open repository is used. The URL of the remote server is specified on the command line If no URL is specified then the URL used by the most recent "pull", "push", or "sync" command is used. ................................................................................ The "USER@" and ":PORT" substrings are optional. The "USER" substring specifies the login user. You will be prompted for the password on the command-line. The PORT specifies the TCP port of the server. The default port is 80. <hr><a href="#tof">ˆ</a> <a name="push">Usage: </a><a href="cmd_push.wiki">fossil push</a> ?URL? ?-R|--repository REPOSITORY? Push changes in the local repository over into a remote repository. See the "pull" command for additional information. <hr><a href="#tof">ˆ</a> <a name="rebuild">Usage: </a><a href="cmd_rebuild.wiki">fossil rebuild</a> REPOSITORY Reconstruct the named repository database from the core records. Run this command after updating the fossil executable in a way that changes the database schema. <hr><a href="#tof">ˆ</a> COMMAND: reconstruct <a name="reconstruct">Usage: </a><a href="cmd_reconstruct.wiki">fossil reconstruct</a> REPOSITORY ORIGIN Creates the REPOSITORY and populates it with the artifacts in the indicated ORIGIN directory. <hr><a href="#tof">ˆ</a> <a name="redo">Usage: </a><a href="cmd_redo.wiki">fossil redo</a> ?FILENAME...? Redo the an update or merge operation that has been undone by the undo command. If FILENAME is specified then restore the changes associated with the named file(s) but otherwise leave the update or merge undone. A single level of undo/redo is supported. The undo/redo stack is cleared by the commit and checkout commands. <hr><a href="#tof">ˆ</a> <a name="revert">Usage: </a><a href="cmd_revert.wiki">fossil revert</a> ?--yes? ?-r CHECKIN? FILE Revert to the current repository version of FILE, or to the version associated with check-in CHECKIN if the -r flag appears. This command will confirm your operation unless the file is missing or the --yes option is used. <hr><a href="#tof">ˆ</a> <a name="server">Usage: </a><a href="cmd_server.wiki">fossil server</a> ?-P|--port TCPPORT? ?REPOSITORY? Or: fossil ui ?-P|--port TCPPORT? ?REPOSITORY? Open a socket and begin listening and responding to HTTP requests on TCP port 8080, or on any other TCP port defined by the -P or --port option. The optional argument is the name of the repository. The repository argument may be omitted if the working directory is within an open checkout. The "ui" command automatically starts a web browser after initializing the web server. <hr><a href="#tof">ˆ</a> COMMAND: settings COMMAND: unset <a name="settings">Usage: </a><a href="cmd_setting.wiki">fossil settings</a> ?PROPERTY? ?VALUE? ?-global? fossil unset PROPERTY ?-global? The "settings" command with no arguments lists all properties and their values. With just a property name it shows the value of that property. ................................................................................ then a direct HTTP connection is used. web-browser A shell command used to launch your preferred web browser when given a URL as an argument. Defaults to "start" on windows, "open" on Mac, and "firefox" on Unix. <hr><a href="#tof">ˆ</a> <a name="status">Usage: </a><a href="cmd_status.wiki">fossil status</a> Report on the status of the current checkout. <hr><a href="#tof">ˆ</a> <a name="sync">Usage: </a><a href="cmd_sync.wiki">fossil sync</a> ?URL? ?-R|--repository REPOSITORY? Synchronize the local repository with a remote repository. This is the equivalent of running both "push" and "pull" at the same time. See the "pull" command for additional information. <hr><a href="#tof">ˆ</a> <a name="tag">Usage: </a><a href="cmd_tag.wiki">fossil tag</a> SUBCOMMAND ... Run various subcommands to control tags and properties fossil tag add ?--raw? TAGNAME CHECK-IN ?VALUE? Add a new tag or property to CHECK-IN. The tag will be usable instead of a CHECK-IN in commands such as ................................................................................ will be taken as an artifact or check-in ID and fossil will probably complain that no such revision was found. However fossil update tag:decaf will assume that "decaf" is a tag/branch name. <hr><a href="#tof">ˆ</a> <a name="timeline">Usage: </a><a href="cmd_timeline.wiki">fossil timeline</a> ?WHEN? ?CHECK-IN|DATETIME? ?-n|--count N? Print a summary of activity going backwards in date and time specified or from the current date and time if no arguments are given. Show as many as N (default 20) check-ins. The WHEN argument can be any unique abbreviation of one of these keywords: ................................................................................ ancestors | parents The CHECK-IN can be any unique prefix of 4 characters or more. The DATETIME should be in the ISO8601 format. For examples: "2007-08-18 07:21:21". You can also say "current" for the current version or "now" for the current time. <hr><a href="#tof">ˆ</a> <a name="undo">Usage: </a><a href="cmd_undo.wiki">fossil undo</a> ?FILENAME...? Undo the most recent update or merge operation. If FILENAME is specified then restore the content of the named file(s) but otherwise leave the update or merge in effect. A single level of undo/redo is supported. The undo/redo stack is cleared by the commit and checkout commands. <hr><a href="#tof">ˆ</a> <a name="update">Usage: </a><a href="cmd_update.wiki">fossil update</a> ?VERSION? ?--latest? The optional argument is a version that should become the current version. If the argument is omitted, then use the leaf of the tree that begins with the current version, if there is only a single leaf. If there are a multiple leaves, the latest is used if the --latest flag is present. This command is different from the "checkout" in that edits are not overwritten. Edits are merged into the new version. <hr><a href="#tof">ˆ</a> <a name="user">Usage: </a><a href="cmd_user.wiki">fossil user</a> SUBCOMMAND ... ?-R|--repository FILE? Run various subcommands on users of the open repository or of the repository identified by the -R or --repository option. fossil user capabilities USERNAME ?STRING? Query or set the capabilities for user USERNAME ................................................................................ deleted. They can be denied all access but they must continue to exist in the database. fossil user password USERNAME Change the web access password for a user. <hr><a href="#tof">ˆ</a> <a name="version">Usage: </a><a href="cmd_version.wiki">fossil version</a> Print the source code version number for the fossil executable. <hr><a href="#tof">ˆ</a> <a name="wiki">Usage: </a><a href="cmd_wiki.wiki">fossil wiki</a> (export|create|commit|list) WikiName Run various subcommands to fetch wiki entries. fossil wiki export PAGENAME ?FILE? Sends the latest version of the PAGENAME wiki entry to the given file or standard output. ................................................................................ fossil wiki diff ?ARTIFACT? ?-f infile[=stdin]? EntryName Diffs the local copy of a page with a given version (defaulting to the head version). </pre></nowiki> <hr><a href="#tof">ˆ</a> <h3>Caveats</h3> This is not actually a reference, it's the start of a reference. There are wikilinks to uncreated pages for the commands. This was created by running the fossil help for each command listed by running fossil help... Duplicate commands are only listed once (I <i>think</i>). There are several bits of <b>fossil</b> that are not addressed in the help for commands (special wiki directories, special users, etc.) so they are (currently) not addressed here. Clarity and brevity may be sacrificed for expediency at the authors indiscretion. All spelling and grammatical mistakes are somebody elses fault.<code> void * </code> prohibited where<code> __C_PLUS_PLUS__ </code>. Title and taxes extra. Not valid in Hooptigonia. |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
1 2 3 4 5 6 7 8 9 10 11 12 .. 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 .. 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 ... 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 ... 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 ... 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 ... 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 ... 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 ... 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 ... 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 ... 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 ... 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 ... 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 ... 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 ... 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 |
<h2>Command Line Interface Reference</h2> This is an easy introduction to the fossil command line interface (cli). It assumes some familiarity with using the command line, and with Source Code Maintenence (SCM) systems—but not <i>too</i> much. If you are trying to find information about fossil's web capabilities, see the <a href="index.wiki">Fossil Home</a> and <a href="wikitheory.wiki">Fossil Wiki</a> pages for pointers. <h3>Things to note</h3> ................................................................................ '-' (hyphen, or dash) character. This is very similar to Tcl. Think of fossil as a shell you invoke and feed a command to, including any options, and it will make more sense. * Any fossil command is acceptable once enough of it has been entered to make the intent unambiguous. 'clo' is a proper prefix of both the 'clone' and 'close' commands, for instance, but 'clon' is enough to make the intent—the 'clone' command—unambiguous. * Pragmatically, a [./concepts.wiki#keyconc | <u>version</u>] in <b>fossil</b> is a 40-character long string of hexadecimal. <b>fossil</b> will be able to figure out which version you want with any <i>distinct</i> prefix of that string which is at least four characters long. <em>Commands which require a version are looking for the string, a distinct prefix of the ................................................................................ understand if you can run a repository, watch it in a browser, and hack around with it in a simplified environment (your tests) with guaranteed and fast access to the sources & docs (your cloned fossil repository). <br /><br /> <br /> <b>You should</b> probably start interacting with fossil at the command line by asking it what it can do: <a name="tof">ˆ</a> <code>$ fossil help</code><nowiki><pre> Usage: fossil help COMMAND. Available COMMANDs:</pre><table width="80%" style="font-family: fixed, courier, monospace;"> <tr> <td><a href="#add">add</a>*</td> ................................................................................ </pre> <b>What follows</b> is a survey of what you get if you type<code> fossil help <i>command</i> </code>for all of the commands listed above. There are links to individual pages for each of them; pages with content (commands marked with a '*' are done) go into the reason for a command in a bit more depth than the program help. <pre> <hr><a href="#tof">ˆ</a> <a name="add">Usage: </a><code><a href="cmd_add.wiki">fossil add</a></code> FILE... Make arrangements to add one or more files to the current checkout at the next commit. <hr><a href="#tof">ˆ</a> <a name="all">Usage: </a><code><a href="cmd_all.wiki">fossil all</a></code> (list|pull|push|rebuild|sync) The ~/.fossil file records the location of all repositories for a user. This command performs certain operations on all repositories that can be useful before or after a period of disconnection operation. On Win32 systems, this file is located in %LOCALAPPDATA%, %APDDATA% or %HOMEPATH% and is named _fossil. ................................................................................ sync Run a "sync" on all repositories Respositories are automatically added to the set of known repositories when one of the following commands against the repository: clone, info, pull, push, or sync <hr><a href="#tof">ˆ</a> <a name="branch">Usage: </a><code><a href="cmd_branch.wiki">fossil branch</a></code> SUBCOMMAND ... ?-R|--repository FILE? Run various subcommands on the branches of the open repository or of the repository identified by the -R or --repository option. fossil branch new BRANCH-NAME BASIS ?-bgcolor COLOR? ................................................................................ Create a new branch BRANCH-NAME off of check-in BASIS. You can optionally give the branch a default color. fossil branch list List all branches <hr><a href="#tof">ˆ</a> <a name="cgi">Usage: </a><a href="cmd_cgi.wiki">fossil cgi</a> SCRIPT The SCRIPT argument is the name of a file that is the CGI script that is being run. The command name, "cgi", may be omitted if the GATEWAY_INTERFACE environment variable is set to "CGI" (which should always be the case for CGI scripts run by a webserver.) The SCRIPT file should look something like this: ................................................................................ #!/usr/bin/fossil repository: /home/somebody/project.db The second line defines the name of the repository. After locating the repository, fossil will generate a webpage on stdout based on the values of standard CGI environment variables. <hr><a href="#tof">ˆ</a> <a name="changes">Usage: </a><a href="cmd_changes.wiki">fossil changes</a> Report on the edit status of all files in the current checkout. See also the "status" and "extra" commands. <hr><a href="#tof">ˆ</a> <a name="checkout">Usage: </a><a href="cmd_checkout.wiki">fossil checkout</a> VERSION ?-f|--force? Check out a version specified on the command-line. This command will not overwrite edited files in the current checkout unless the --force option appears on the command-line. See also the "update" command. <hr><a href="#tof">ˆ</a> <a name="commit">Usage: </a><a href="cmd_commit.wiki">fossil commit</a> ?-m COMMENT? ?--nosign? ?FILE...? fossil ci ... (as above) Create a new version containing all of the changes in the current checkout. You will be prompted to enter a check-in comment unless the "-m" option is used to specify a comment line. You will be prompted for your GPG passphrase in order to sign the new manifest unless the "--nosign" option is used. All files that have changed will be committed unless some subset of files is specified on the command line. <hr><a href="#tof">ˆ</a> <a name="clean">Usage: </a><a href="cmd_clean.wiki">fossil clean</a> ?-all? Delete all "extra" files in the source tree. "Extra" files are files that are not officially part of the checkout. See also the "extra" command. This operation cannot be undone. You will be prompted before removing each file. If you are sure you wish to remove all "extra" files you can specify the optional -all flag. <hr><a href="#tof">ˆ</a> <a name="clone">Usage: </a><a href="cmd_clone.wiki">fossil clone</a> URL FILENAME Make a clone of a repository specified by URL in the local file named FILENAME. <hr><a href="#tof">ˆ</a> <a name="close">Usage: </a><a href="cmd_close.wiki">fossil close</a> ?-f|--force? The opposite of "open". Close the current database connection. Require a -f or --force flag if there are unsaved changed in the current check-out. <hr><a href="#tof">ˆ</a> <a name="configuration">Usage: </a><a href="cmd_configure.wiki">fossil configuration</a> METHOD ... Where METHOD is one of: export import merge pull push reset. All methods accept the -R or --repository option to specific a repository. fossil configuration export AREA FILENAME Write to FILENAME exported configuraton information for AREA. ................................................................................ Restore the configuration to the default. AREA as above. WARNING: Do not import, merge, or pull configurations from an untrusted source. The inbound configuration is not checked for safety and can introduce security vulnerabilities. <hr><a href="#tof">ˆ</a> COMMAND: deconstruct <a name="deconstruct">Usage: </a><a href="cmd_deconstruct.wiki">fossil deconstruct</a> ?-R|--repository REPOSITORY? DESTINATION Populates the indicated DESTINATION directory with copies of all artifcats contained within the repository. Artifacts are named AA/bbbbb where AA is the first 2 characters of the artifact ID and bbbbb is the remaining 38 characters. <hr><a href="#tof">ˆ</a> <a name="rm">Usage: </a><a href="cmd_rm.wiki">fossil rm</a> FILE... or: fossil del FILE... Remove one or more files from the tree. <hr><a href="#tof">ˆ</a> <a name="descendants">Usage: </a><a href="cmd_descendants.wiki">fossil descendants</a> ?CHECKIN-ID? Find all leaf descendants of the check-in specified or if the argument is omitted, of the check-in currently checked out. <hr><a href="#tof">ˆ</a> <a name="diff">Usage: </a><a href="cmd_diff.wiki">fossil diff</a>|gdiff ?-i? ?-r REVISION? FILE... Show the difference between the current version of a file (as it exists on disk) and that same file as it was checked out. diff will show a textual diff while gdiff will attempt to run a graphical diff command that you have setup. If the choosen command is not yet configured, the internal textual diff command will be ................................................................................ fossil setting gdiff-command tkdiff fossil setting gdiff-command eskill22 fossil setting gdiff-command tortoisemerge fossil setting gdiff-command meld fossil setting gdiff-command xxdiff fossil setting gdiff-command kdiff3 <hr><a href="#tof">ˆ</a> <a name="extra">Usage: </a><a href="cmd_extra.wiki">fossil extra</a> Print a list of all files in the source tree that are not part of the current checkout. See also the "clean" command. <hr><a href="#tof">ˆ</a> <a name="help">Usage: </a><a href="cmd_help.wiki">fossil help</a> COMMAND Display information on how to use COMMAND <hr><a href="#tof">ˆ</a> <a name="http">Usage: </a><a href="cmd_http.wiki">fossil http</a> REPOSITORY Handle a single HTTP request appearing on stdin. The resulting webpage is delivered on stdout. This method is used to launch an HTTP request handler from inetd, for example. The argument is the name of the repository. <hr><a href="#tof">ˆ</a> <a name="info">Usage: </a><a href="cmd_info.wiki">fossil info</a> ?ARTIFACT-ID|FILENAME? With no arguments, provide information about the current tree. If an argument is specified, provide information about the object in the respository of the current tree that the argument refers to. Or if the argument is the name of a repository, show information about that repository. <hr><a href="#tof">ˆ</a> <a name="leaves">Usage: </a><a href="cmd_leaves.wiki">fossil leaves</a> Find leaves of all branches. <hr><a href="#tof">ˆ</a> <a name="ls">Usage: </a><a href="cmd_ls.wiki">fossil ls</a> Show the names of all files in the current checkout <hr><a href="#tof">ˆ</a> <a name="merge">Usage: </a><a href="cmd_merge.wiki">fossil merge</a> VERSION The argument is a version that should be merged into the current checkout. Only file content is merged. The result continues to use the file and directory names from the current check-out even if those names might have been changed in the branch being merged in. <hr><a href="#tof">ˆ</a> <a name="mv">Usage: </a><a href="cmd_mv.wiki">fossil mv|rename</a> OLDNAME NEWNAME or: fossil mv|rename OLDNAME... DIR Move or rename one or more files within the tree This command does not rename the files on disk. All this command does is record the fact that filenames have changed so that appropriate notations can be made at the next commit/checkin. <hr><a href="#tof">ˆ</a> <a name="new">Usage: </a><a href="cmd_new.wiki">fossil new</a> FILENAME Create a repository for a new project in the file named FILENAME. This command is distinct from "clone". The "clone" command makes a copy of an existing project. This command starts a new project. <hr><a href="#tof">ˆ</a> <a name="open">Usage: </a><a href="cmd_open.wiki">fossil open</a> FILENAME Open a connection to the local repository in FILENAME. A checkout for the repository is created with its root at the working directory. See also the "close" command. <hr><a href="#tof">ˆ</a> <a name="rstats">Usage: </a><a href="cmd_rstats.wiki">fossil rstats</a> Deliver a report of the repository statistics for the current checkout. <hr><a href="#tof">ˆ</a> <a name="pull">Usage: </a><a href="cmd_pull.wiki">fossil pull</a> ?URL? ?-R|--respository REPOSITORY? Pull changes in a remote repository into the local repository. The repository is identified by the -R or --repository option. If there is no such option then the open repository is used. The URL of the remote server is specified on the command line If no URL is specified then the URL used by the most recent "pull", "push", or "sync" command is used. ................................................................................ The "USER@" and ":PORT" substrings are optional. The "USER" substring specifies the login user. You will be prompted for the password on the command-line. The PORT specifies the TCP port of the server. The default port is 80. <hr><a href="#tof">ˆ</a> <a name="push">Usage: </a><a href="cmd_push.wiki">fossil push</a> ?URL? ?-R|--repository REPOSITORY? Push changes in the local repository over into a remote repository. See the "pull" command for additional information. <hr><a href="#tof">ˆ</a> <a name="rebuild">Usage: </a><a href="cmd_rebuild.wiki">fossil rebuild</a> REPOSITORY Reconstruct the named repository database from the core records. Run this command after updating the fossil executable in a way that changes the database schema. <hr><a href="#tof">ˆ</a> COMMAND: reconstruct <a name="reconstruct">Usage: </a><a href="cmd_reconstruct.wiki">fossil reconstruct</a> REPOSITORY ORIGIN Creates the REPOSITORY and populates it with the artifacts in the indicated ORIGIN directory. <hr><a href="#tof">ˆ</a> <a name="redo">Usage: </a><a href="cmd_redo.wiki">fossil redo</a> ?FILENAME...? Redo the an update or merge operation that has been undone by the undo command. If FILENAME is specified then restore the changes associated with the named file(s) but otherwise leave the update or merge undone. A single level of undo/redo is supported. The undo/redo stack is cleared by the commit and checkout commands. <hr><a href="#tof">ˆ</a> <a name="revert">Usage: </a><a href="cmd_revert.wiki">fossil revert</a> ?--yes? ?-r CHECKIN? FILE Revert to the current repository version of FILE, or to the version associated with check-in CHECKIN if the -r flag appears. This command will confirm your operation unless the file is missing or the --yes option is used. <hr><a href="#tof">ˆ</a> <a name="server">Usage: </a><a href="cmd_server.wiki">fossil server</a> ?-P|--port TCPPORT? ?REPOSITORY? Or: fossil ui ?-P|--port TCPPORT? ?REPOSITORY? Open a socket and begin listening and responding to HTTP requests on TCP port 8080, or on any other TCP port defined by the -P or --port option. The optional argument is the name of the repository. The repository argument may be omitted if the working directory is within an open checkout. The "ui" command automatically starts a web browser after initializing the web server. <hr><a href="#tof">ˆ</a> COMMAND: settings COMMAND: unset <a name="settings">Usage: </a><a href="cmd_setting.wiki">fossil settings</a> ?PROPERTY? ?VALUE? ?-global? fossil unset PROPERTY ?-global? The "settings" command with no arguments lists all properties and their values. With just a property name it shows the value of that property. ................................................................................ then a direct HTTP connection is used. web-browser A shell command used to launch your preferred web browser when given a URL as an argument. Defaults to "start" on windows, "open" on Mac, and "firefox" on Unix. <hr><a href="#tof">ˆ</a> <a name="status">Usage: </a><a href="cmd_status.wiki">fossil status</a> Report on the status of the current checkout. <hr><a href="#tof">ˆ</a> <a name="sync">Usage: </a><a href="cmd_sync.wiki">fossil sync</a> ?URL? ?-R|--repository REPOSITORY? Synchronize the local repository with a remote repository. This is the equivalent of running both "push" and "pull" at the same time. See the "pull" command for additional information. <hr><a href="#tof">ˆ</a> <a name="tag">Usage: </a><a href="cmd_tag.wiki">fossil tag</a> SUBCOMMAND ... Run various subcommands to control tags and properties fossil tag add ?--raw? TAGNAME CHECK-IN ?VALUE? Add a new tag or property to CHECK-IN. The tag will be usable instead of a CHECK-IN in commands such as ................................................................................ will be taken as an artifact or check-in ID and fossil will probably complain that no such revision was found. However fossil update tag:decaf will assume that "decaf" is a tag/branch name. <hr><a href="#tof">ˆ</a> <a name="timeline">Usage: </a><a href="cmd_timeline.wiki">fossil timeline</a> ?WHEN? ?CHECK-IN|DATETIME? ?-n|--count N? Print a summary of activity going backwards in date and time specified or from the current date and time if no arguments are given. Show as many as N (default 20) check-ins. The WHEN argument can be any unique abbreviation of one of these keywords: ................................................................................ ancestors | parents The CHECK-IN can be any unique prefix of 4 characters or more. The DATETIME should be in the ISO8601 format. For examples: "2007-08-18 07:21:21". You can also say "current" for the current version or "now" for the current time. <hr><a href="#tof">ˆ</a> <a name="undo">Usage: </a><a href="cmd_undo.wiki">fossil undo</a> ?FILENAME...? Undo the most recent update or merge operation. If FILENAME is specified then restore the content of the named file(s) but otherwise leave the update or merge in effect. A single level of undo/redo is supported. The undo/redo stack is cleared by the commit and checkout commands. <hr><a href="#tof">ˆ</a> <a name="update">Usage: </a><a href="cmd_update.wiki">fossil update</a> ?VERSION? ?--latest? The optional argument is a version that should become the current version. If the argument is omitted, then use the leaf of the tree that begins with the current version, if there is only a single leaf. If there are a multiple leaves, the latest is used if the --latest flag is present. This command is different from the "checkout" in that edits are not overwritten. Edits are merged into the new version. <hr><a href="#tof">ˆ</a> <a name="user">Usage: </a><a href="cmd_user.wiki">fossil user</a> SUBCOMMAND ... ?-R|--repository FILE? Run various subcommands on users of the open repository or of the repository identified by the -R or --repository option. fossil user capabilities USERNAME ?STRING? Query or set the capabilities for user USERNAME ................................................................................ deleted. They can be denied all access but they must continue to exist in the database. fossil user password USERNAME Change the web access password for a user. <hr><a href="#tof">ˆ</a> <a name="version">Usage: </a><a href="cmd_version.wiki">fossil version</a> Print the source code version number for the fossil executable. <hr><a href="#tof">ˆ</a> <a name="wiki">Usage: </a><a href="cmd_wiki.wiki">fossil wiki</a> (export|create|commit|list) WikiName Run various subcommands to fetch wiki entries. fossil wiki export PAGENAME ?FILE? Sends the latest version of the PAGENAME wiki entry to the given file or standard output. ................................................................................ fossil wiki diff ?ARTIFACT? ?-f infile[=stdin]? EntryName Diffs the local copy of a page with a given version (defaulting to the head version). </pre></nowiki> <hr><a href="#tof">ˆ</a> <h3>Caveats</h3> This is not actually a reference, it's the start of a reference. There are wikilinks to uncreated pages for the commands. This was created by running the fossil help for each command listed by running fossil help... Duplicate commands are only listed once (I <i>think</i>). There are several bits of <b>fossil</b> that are not addressed in the help for commands (special wiki directories, special users, etc.) so they are (currently) not addressed here. Clarity and brevity may be sacrificed for expediency at the authors indiscretion. All spelling and grammatical mistakes are somebody elses fault.<code> void * </code> prohibited where<code> __C_PLUS_PLUS__ </code>. Title and taxes extra. Not valid in Hooptigonia. |
Changes to www/reviews.wiki.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
<title>Reviews</title>
<b>External links:</b>
* [http://sheddingbikes.com/posts/1276624594.html | Why I Use Fossil]
by Zed A. Shaw.
* [http://nixtu.blogspot.com/2010/03/fossil-dvcs-on-go-first-impressions.html |
Fossil DVCS on the Go - First Impressions]
by Juho Vepsäläinen.
* [http://blog.fupps.com/2010/12/04/exploring-the-fossil-dvcs |
Exploring the Fossil DVCS] by Jan-Piet Mens.
* [http://blog.mired.org/2011/02/fossil-sweet-spot-in-vcs-space.html |
Fossil - a sweet spot in the VCS space] by Mike Meyer.
* [http://blog.s11n.net/?p=72|Four reasons to take a closer look at the Fossil SCM] by Stephan Beal
<b>See Also:</b>
|
< > |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
<title>Reviews</title>
<b>External links:</b>
* [http://sheddingbikes.com/posts/1276624594.html | Why I Use Fossil]
by Zed A. Shaw.
* [http://nixtu.blogspot.com/2010/03/fossil-dvcs-on-go-first-impressions.html |
Fossil DVCS on the Go - First Impressions]
* [http://blog.fupps.com/2010/12/04/exploring-the-fossil-dvcs |
by Juho Vepsäläinen.
Exploring the Fossil DVCS] by Jan-Piet Mens.
* [http://blog.mired.org/2011/02/fossil-sweet-spot-in-vcs-space.html |
Fossil - a sweet spot in the VCS space] by Mike Meyer.
* [http://blog.s11n.net/?p=72|Four reasons to take a closer look at the Fossil SCM] by Stephan Beal
<b>See Also:</b>
|