Fossil

Check-in [1eb067d4]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Adjust some wikilinks, clean up main ref page, add "new" command.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 1eb067d45626121fb666d111b654eaf47943c351
User & Date: kejoki 2008-12-12 21:55:46
Context
2008-12-12
22:19
/timeline.rss now accepts the same filter parameters as /timeline (e.g. y=ci for commits and y=w for wiki) check-in: 90adbd84 user: stephan tags: trunk
21:55
Adjust some wikilinks, clean up main ref page, add "new" command. check-in: 1eb067d4 user: kejoki tags: trunk
2008-12-09
20:25
Change the add command CLI doc to reflect recursive add of directories. check-in: 83447b7b user: kejoki tags: trunk
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to kktodo.wiki.

     1      1   <h3>kkinnell</h3>
     2      2   
     3      3   .plan -- <i>Fossil, the DG</i> Bwahahahaha! The cover art could be an <i>homo erectus</i> skull lying on some COBOL code...
     4      4   
     5      5     1.  Command line interface reference docs
     6      6        <ul>
     7         -         <li> Finish initial pages.</li>
            7  +         <li> <font color="#bb4466">Finish initial pages.</font></li>
     8      8   	 <li> Start on tech-spec (serious, not "chatty") reference pages.</li>
     9      9   	 <li> Edit, edit, edit.</li>
    10     10        </ul>
    11     11   
    12     12     2.  Support docs
    13     13        <ul>
    14     14   	 <li>Basic explanation of Distributed SCM.</i>
................................................................................
    23     23   	     <ul>
    24     24   	         <li>Open, close, commit, checkout, update, merge.</li>
    25     25   	     </ul>
    26     26   	     </li>
    27     27   	     <li>Hmmm.  Experimenting.</li>
    28     28   	     <ul>
    29     29   	         <li>The road less travelled, or where'd that
    30         -		 fork come from?</l>
           30  +		 fork come from?</li>
    31     31   	     </ul>
    32     32   	     <li>Oops!  Going back in time.</li>
           33  +	     <ul>
           34  +	         <li>Versions</li>
           35  +		 <ul>
           36  +		     <li>What <i>is</i> a version?</li>
           37  +		     <li>Is it a "version" or a "tag"?</li>
           38  +		     <li>DSCM redux: Revisionist versioning.</li>
           39  +		 </ul>
           40  +	     </ul>
    33     41   	 </ul>
    34     42   	 </li>
    35     43            <li>Basic explanation of <i>merge</i>.
    36     44   	 <ol>
    37         -	     <li>Leaves, branches and baselines.</li>
           45  +	     <li>Leaves, branches and baselines: We want a shrubbery!</li>
    38     46   	     <li><i>update</i> merges vs. <i>merge</i> merges.
    39     47   	     All merges are equal, but some are more equal than others.</li>
    40     48   	 </ol>
    41     49   	 </li>
    42     50        </ul>
           51  +
           52  +  3.  Configuration
    43     53   
    44     54     42.  General
    45     55        <ul>
    46     56   	 <li>Co-ordinate style and tone with drh, other devs. (documentation
    47     57            standard?  yuck.)</li>
    48     58        </ul>
    49     59   

Changes to www/cmd_all.wiki.

     2      2   
     3      3   The <code>all</code> command will let you perform (some) commands on
     4      4   <em>all</em> of your repositories, and provides a way of finding all
     5      5   of your repositories as well.
     6      6   
     7      7   There are some commands you might especially want to perform on every
     8      8   repository you've got, once in a while.  <code> fossil&nbsp;all
     9         -</code> includes four of the most likely as sub-commands: 
    10         -<code><a href="cmd_pull.wiki">pull</a></code>,
    11         -<code><a href="cmd_push.wiki">push</a></code>,
    12         -<code><a href="cmd_rebuild.wiki">rebuild</a></code> and 
    13         -<code><a href="cmd_sync.wiki">sync</a></code>.
            9  +</code> includes four of the most likely as sub-commands:
           10  +[./cmd_pull.wiki | <code>pull</code>],
           11  +[./cmd_push.wiki | <code>push</code>],
           12  +[./cmd_rebuild.wiki | <code>rebuild</code>] and
           13  +[./cmd_sync.wiki | <code>sync</code>].
    14     14   
    15     15   Follow the links to find out what each of those do, and then a moment
    16     16   of thought will tell you why you might want to have them available for
    17     17   all repositories.
    18     18   
    19     19   Certainly you'll want your repositories all rebuilt when you upgrade
    20     20   <b>fossil</b> after there has been a change in the repository
................................................................................
    41     41   moving your repositories around.  This is easy to do inadvertently if
    42     42   you have a cavalier attitude about repos, but you'll know pretty
    43     43   quickly that you've done it&#8212;many commands you try to use from
    44     44   inside of a checkout won't work correctly.  The <i>.fossil</i> file is
    45     45   an <b>sqlite</b> db file which fossil uses to keeping track of
    46     46   repository locations. Advice: if you move your repositories around,
    47     47   let fossil know you did;
    48         -<code><a href="cmd_close.wiki">close</a></code> them before you move
    49         -them, and then <code><a href="cmd_open.wiki">open</a></code> them from
           48  +[./cmd_close.wiki | <code>close</code>] them before you move
           49  +them, and then [./cmd_open.wiki | <code>open</code>] them from
    50     50   their new locations.
    51     51   
    52         -See also: <a href="cmd_pull.wiki">fossil pull</a>,
    53         -<a href="cmd_push.wiki">fossil push</a>,
    54         -<a href="cmd_rebuild.wiki">fossil rebuild</a>,
    55         -<a href="cmd_sync.wiki">fossil sync</a>,
    56         -<a href="cmd_open.wiki">fossil open</a>,
    57         -<a href="cmd_close.wiki">fossil close</a>,
    58         -<a href="reference.wiki">Reference</a>,
    59         -<b><a href="http://www.sqlite.org">sqlite</a></b>
           52  +See also: [./cmd_pull.wiki | fossil pull],
           53  +[./cmd_push.wiki | fossil push],
           54  +[./cmd_rebuild.wiki | fossil rebuild],
           55  +[./cmd_sync.wiki | fossil sync],
           56  +[./cmd_open.wiki | fossil open],
           57  +[./cmd_close.wiki | fossil close],
           58  +[./reference.wiki | Reference],
           59  +[http://www.sqlite.org | <b>SQLite</b>]

Changes to www/cmd_extra.wiki.

     5      5   
     6      6   Extra files are files that exist in a checked-out project, but don't belong to
     7      7   the repository.
     8      8   
     9      9   The <code>fossil extra</code> command will get you a list of these files.
    10     10   
    11     11   This is convenient for figuring out if you've <code>
    12         -<a href="cmd_add.wiki">add</a></code>ed every file that needs to be
           12  +[./cmd_add.wiki | add]</code>ed every file that needs to be
    13     13   
    14     14   in the repository before you do a commit.  It will also tell you what
    15         -will be removed if you <code><a href="cmd_clean.wiki">clean</a></code>
           15  +will be removed if you [./cmd_clean.wiki | <code>clean</code>]
    16     16   the project.
    17     17   
    18     18   Suppose, for example, you have a "noodle.src" file as a scratch pad
    19     19   for source code, and you don't want to include your latest
    20     20   hare-brained ideas in the repository?  You don't <code>add</code> it
    21     21   to the repository, of course&#8212;though there are ways you might add
    22     22   it unintentionally.  If your project is big, and you want to find
................................................................................
    25     25   give you a list.
    26     26   
    27     27   If you don't think this is all that useful, then you've never had to write
    28     28   a shell script that only affects project files and leaves everything
    29     29   else alone.  ;)
    30     30   
    31     31   The <code>extra</code> command is almost, but not quite entirely, the exact
    32         -opposite of the <code><a href="cmd_ls.wiki">ls</a></code> command.
           32  +opposite of the [./cmd_ls.wiki | <code>ls</code>] command.
    33     33   
    34         -See also: <a href="cmd_status.wiki">fossil status</a>,
    35         -<a href="cmd_ls.wiki">fossil ls</a>,
    36         -<a href="cmd_changes.wiki">fossil changes</a>,
    37         -<a href="cmd_clean.wiki">fossil clean</a>,
    38         -<a href="reference.wiki">Reference</a>
           34  +See also: [./cmd_status.wiki | fossil status],
           35  +[./cmd_ls.wiki | fossil ls],
           36  +[./cmd_changes.wiki | fossil changes],
           37  +[./cmd_clean.wiki | fossil clean],
           38  +[./reference.wiki | Reference]

Changes to www/cmd_ls.wiki.

     1      1   <h2>ls</h2>
     2      2   
     3      3   The <code>ls</code><a href="#notes">*</a> command is informational, it doesn't do anything to
     4      4   a checked-out project, but it tells you something about it.
     5      5   
     6         -A project consists of a "source tree" of "artifacts" (see <a href="concepts.wiki">Fossil concepts</a>.)
            6  +A project consists of a "source tree" of "artifacts" (see [./concepts.wiki | Fossil concepts].)
     7      7   From a practical standpoint this is a set of files and directories rooted
     8      8   at a main project directory.  The files that are under source control aren't
     9      9   particularly distinguishable from those that aren't.  The <code>ls</code> and
    10     10   <code>extra</code> commands provide this information.
    11     11   
    12     12   <code>fossil ls</code> produces a listing of the files which are under source
    13     13   control <i>and</i> their status within the repository.  The output is a simple
................................................................................
    16     16   
    17     17   It's important to realize that this is the status <i>relative to the repository</i>,
    18     18   it's the status as <b>fossil</b> sees it and has nothing to do with
    19     19   filesystem status.  If you're new to source-management/version-control
    20     20   systems, you'll probably get bit by this concept-bug at least once.
    21     21   
    22     22   To really see the difference, issue an <code>ls</code> before and after doing
    23         -a <a href="cmd_commit.wiki"><code>commit</code></a>.  Before, the status of files may be any of the three,
           23  +a [./cmd_commit.wiki | <code>commit</code>].  Before, the status of files may be any of the three,
    24     24   but after <code>commit</code>ting changes the status will be UNCHANGED "across
    25     25   the board."
    26     26   
    27     27   By way of example, here's what I see if I <code>fossil ls</code> in the
    28     28   directory where I have checked out my testing repository:
    29     29   <nowiki><pre>
    30     30       $ fossil ls
................................................................................
    37     37       $ ls
    38     38       feegboing  fossil_docs.txt  manifest.uuid  noodle.txt
    39     39       _FOSSIL_   manifest         nibcrod
    40     40   </pre></nowiki>
    41     41   
    42     42   The <code>ls</code> command is almost, but not quite entirely, the exact
    43     43   opposite of the
    44         -<a href="cmd_extra.wiki"><code>extra</code> command</a>.
           44  +[./cmd_extra.wiki | <code>extra</code> command].
    45     45   
    46     46   <a name="notes">Notes:</a>
    47     47     *  If you come from the <b>Windows</b> world, it will help to know that 'ls' is the usual <b>unix</b> command for listing a directory.
    48     48     *  There are more states for a file to be in than those listed, including MISSING, EDITED, RENAMED and a couple of others.
    49     49   
    50         -See also: <a href="cmd_add.wiki">fossil add</a>, <a href="rm.wiki">
    51         -fossil rm</a>, <a href="cmd_extra.wiki">fossil extra</a>, 
    52         -<a href="cmd_commit.wiki">fossil commit</a>, 
    53         -<a href="concepts.wiki">Fossil concepts</a>, 
    54         -<a href="reference.wiki">Reference</a>
           50  +See also: [./cmd_add.wiki | fossil add],
           51  +[./rm.wiki | fossil rm],
           52  +[./cmd_extra.wiki | fossil extra],
           53  +[./cmd_commit.wiki | fossil commit],
           54  +[./concepts.wiki | Fossil concepts],
           55  +[./reference.wiki | Reference]

Added www/cmd_new.wiki.

            1  +<h2>new</h2>
            2  +
            3  +The <code>new</code> command allows you to create a brand new
            4  +repository.
            5  +
            6  +Pragmatically, this means that an SQLite database is created with
            7  +whatever name you specified, and set up with the appropriate tables
            8  +and initial data.
            9  +
           10  +There's not much to <code>new</code>, it's what happens afterward that
           11  +gets a project going:
           12  +
           13  +  Once you have a new repository file, you need to create and cd to a
           14  +  directory in which you will store your files, or move into an
           15  +  existing directory which contains the files for a project.
           16  +
           17  +  Then, you need to [./cmd_open.wiki | <code>open</code>] the new
           18  +  repository, and get the server running so you can set up the project
           19  +  name and so forth.
           20  +
           21  +  Finally, you'll [./cmd_add.wiki | <code>add</code>] files to it.  If
           22  +  you are adding exisiting files, you can add them individually, via
           23  +  globbing from the shell, or by adding the directory (which will add
           24  +  all of the directory's file-system descendants recursively.)
           25  +
           26  +But you can't do all that until you create a repository file with
           27  +<code>new</code>.
           28  +
           29  +See also: [./cmd_open.wiki | fossil open],
           30  +[./cmd_add.wiki | fossil add],
           31  +[./cmd_server.wiki | fossil ui],
           32  +[./reference.wiki | Reference]

Changes to www/cmd_update.wiki.

     1      1   <h2>update</h2>
     2      2   
     3      3   What do you do if you have changes out on a repository and
     4      4   you want them merged with your checkout?
     5      5   
     6         -You use the <code>update</code> command, that's what.
            6  +You use the <code>update</code> command.
     7      7   
     8         -<b>fossil</b> can <a href="about_checkout.wiki">overwrite</a> any
            8  +<b>fossil</b> can [./about_checkout.wiki | overwrite] any
     9      9   changes you've made to your checkout, or it can
    10         -<a href="about_merge.wiki">merge</a> whatever changes have occurred
           10  +[./about_merge.wiki | merge] whatever changes have occurred
    11     11   in the repo into your checkout.
    12     12   
    13     13   Update <em>merges</em> changes from the repository into your checkout.
    14     14   
    15     15   <b>fossil</b> uses a simple conflict resolution strategy for merges:
    16     16   the latest change wins.
    17     17   
    18         -Local intranet <code><a href="cmd_commit.wiki">commit</a></code>s
           18  +Local intranet <code>[./cmd_commit.wiki | commit]</code>s
    19     19   (by someone else)
    20         -or Net <code><a href="cmd_pull.wiki">pull</a></code>s from a server
           20  +or Net <code>[./cmd_pull.wiki | pull]</code>s from a server
    21     21   will usually require a <code>fossil&nbsp;update</code> afterward.
    22     22   
    23     23   Local commits are likely to be made with
    24         -<a href="cmd_settings.wiki#autosync">automatic syncing</a>
           24  +[./cmd_settings.wiki#autosync | automatic syncing]
    25     25   set to "on", however, so if you don't use <b>fossil</b> for Net-wide
    26     26   projects you may never have to use <code>update</code>.
    27     27   
    28         -See also: <a href="cmd_pull.wiki">fossil pull</a>,
    29         -<a href="cmd_commit.wiki">fossil commit</a>,
    30         -<a href="cmd_settings.wiki#autosync">fossil setting</a> (autosync),
    31         -<i><a href="about_checkout.wiki">checkouts</a></i>,
    32         -<i><a href="about_merge.wiki">merging</a></i>,
    33         -<a href="reference.wiki">Reference</a>
           28  +See also: [./cmd_pull.wiki | fossil pull],
           29  +[./cmd_commit.wiki | fossil commit],
           30  +[./cmd_settings.wiki#autosync | fossil setting] (autosync),
           31  +[./about_checkout.wiki | <i>checkouts</i>],
           32  +[./about_merge.wiki | <i>merging</i>],
           33  +[./reference.wiki | Reference]

Changes to www/reference.wiki.

    18     18   
    19     19     *  Any fossil command is acceptable once enough of it has been
    20     20     entered to make the intent unambiguous.  'clo' is a proper prefix of
    21     21     both the 'clone' and 'close' commands, for instance, but 'clon' is
    22     22     enough to make the intent&#8212;the 'clone' command&#8212;unambiguous.
    23     23   
    24     24     You should probably start interacting with fossil at the command line
    25         -  by asking it what it can do:&nbsp;&nbsp;&nbsp;&nbsp;<a name="tof">&#7547;</a>
           25  +  by asking it what it can do:&nbsp;&nbsp;&nbsp;&nbsp;<a name="tof">&#710;</a>
    26     26   
    27     27     <code>$ fossil help</code><nowiki><pre>
    28     28   Usage: fossil help COMMAND.
    29     29   Available COMMANDs:</pre><table width="80%" style="font-family: fixed, courier, monospace; ">
    30     30         <tr>
    31     31   	<td><a href="#add">add</a></td>
    32     32   	<td><a href="#configure">configuration</a></td>
................................................................................
    91     91         <tr>
    92     92   	<td><a href="#commit">commit</a></td>
    93     93   	<td><a href="#info">info</a></td>
    94     94   	<td><a href="#reconstruct">reconstruct</a></td>
    95     95   	<td><a href="#timeline">timeline</a></td>
    96     96         </tr>
    97     97       </table><nowiki><pre>
    98         -This is fossil version [c66ffba6da] 2008-11-10 19:54:53 UTC
           98  +This is fossil version [2be82dcc2a] 2008-12-07 18:48:09 UTC
    99     99   </pre>
   100    100   <b>What follows</b> is a survey of what you get if you type<code>
   101    101   fossil&nbsp;help&nbsp;<i>command</i> </code>for all of the
   102    102   commands listed above.  There are links to individual pages for each
   103    103   of them; pages with content (not all of them are done) go into the command
   104    104   in a bit more depth than the program help.
   105    105   <pre>
   106         -
   107         -    <a name="add">Usage: </a><code><a href="cmd_add.wiki">fossil add</a></code> FILE...    <a href="#tof">&#7547;</a>
   108         -
          106  +<hr><a href="#tof">&#710;</a>
          107  +    <a name="add">Usage: </a><code><a href="cmd_add.wiki">fossil add</a></code> FILE...
   109    108       Make arrangements to add one or more files to the current checkout
   110    109       at the next commit.
   111    110   
   112         -
   113         -    <a name="all">Usage: </a><code><a href="cmd_all.wiki">fossil all</a></code> (list|pull|push|rebuild|sync)    <a href="#tof">&#7547;</a>
   114         -
          111  +<hr><a href="#tof">&#710;</a>
          112  +    <a name="all">Usage: </a><code><a href="cmd_all.wiki">fossil all</a></code> (list|pull|push|rebuild|sync)
   115    113       The ~/.fossil file records the location of all repositories for a
   116    114       user.  This command performs certain operations on all repositories
   117    115       that can be useful before or after a period of disconnection operation.
   118    116       Available operations are:
   119    117   
   120    118       list       Display the location of all repositories
   121    119   
................................................................................
   127    125   
   128    126       sync       Run a "sync" on all repositories
   129    127   
   130    128       Respositories are automatically added to the set of known repositories
   131    129       when one of the following commands against the repository: clone, info,
   132    130       pull, push, or sync
   133    131   
   134         -
   135         -    <a name="cgi">Usage: </a><a href="cmd_cgi">fossil cgi</a> SCRIPT    <a href="#tof">&#7547;</a>
   136         -
          132  +<hr><a href="#tof">&#710;</a>
          133  +    <a name="cgi">Usage: </a><a href="cmd_cgi">fossil cgi</a> SCRIPT
   137    134       The SCRIPT argument is the name of a file that is the CGI script
   138    135       that is being run.  The command name, "cgi", may be omitted if
   139    136       the GATEWAY_INTERFACE environment variable is set to "CGI" (which
   140    137       should always be the case for CGI scripts run by a webserver.)  The
   141    138       SCRIPT file should look something like this:
   142    139   
   143    140       #!/usr/bin/fossil
   144    141       repository: /home/somebody/project.db
   145    142   
   146    143       The second line defines the name of the repository.  After locating
   147    144       the repository, fossil will generate a webpage on stdout based on
   148    145       the values of standard CGI environment variables.
   149    146   
   150         -
   151         -    <a name="changes">Usage: </a><a href="cmd_changes">fossil changes</a>    <a href="#tof">&#7547;</a>
   152         -
          147  +<hr><a href="#tof">&#710;</a>
          148  +    <a name="changes">Usage: </a><a href="cmd_changes">fossil changes</a>
   153    149       Report on the edit status of all files in the current checkout.
   154    150       See also the "status" and "extra" commands.
   155    151   
   156         -
   157         -    <a name="checkout">Usage: </a><a href="checkout">fossil checkout</a> VERSION ?-f|--force?    <a href="#tof">&#7547;</a>
   158         -
          152  +<hr><a href="#tof">&#710;</a>
          153  +    <a name="checkout">Usage: </a><a href="checkout">fossil checkout</a> VERSION ?-f|--force?
   159    154       Check out a version specified on the command-line.  This command
   160    155       will not overwrite edited files in the current checkout unless
   161    156       the --force option appears on the command-line.
   162    157   
   163    158       See also the "update" command.
   164    159   
   165         -
   166         -    <a name="commit">Usage: </a><a href="cmd_commit.wiki">fossil commit</a> ?-m COMMENT? ?--nosign? ?FILE...?    <a href="#tof">&#7547;</a>
   167         -    fossil ci  ...  (as above)
          160  +<hr><a href="#tof">&#710;</a>
          161  +    <a name="commit">Usage: </a><a href="cmd_commit.wiki">fossil commit</a> ?-m COMMENT? ?--nosign? ?FILE...?    fossil ci  ...  (as above)
   168    162   
   169    163       Create a new version containing all of the changes in the current
   170    164       checkout.  You will be prompted to enter a check-in comment unless
   171    165       the "-m" option is used to specify a comment line.  You will be
   172    166       prompted for your GPG passphrase in order to sign the new manifest
   173    167       unless the "--nosign" options is used.  All files that have
   174    168       changed will be committed unless some subset of files is specified
   175    169       on the command line.
   176    170   
   177         -
   178         -    <a name="clean">Usage: </a><a href="cmd_clean.wiki">fossil clean</a> ?-all?    <a href="#tof">&#7547;</a>
   179         -
          171  +<hr><a href="#tof">&#710;</a>
          172  +    <a name="clean">Usage: </a><a href="cmd_clean.wiki">fossil clean</a> ?-all?
   180    173       Delete all "extra" files in the source tree.  "Extra" files are
   181    174       files that are not officially part of the checkout.  See also
   182    175       the "extra" command. This operation cannot be undone.
   183    176   
   184    177       You will be prompted before removing each file. If you are
   185    178       sure you wish to remove all "extra" files you can specify the
   186    179       optional -all flag.
   187    180   
   188         -
   189         -    <a name="clone">Usage: </a><a href="cmd_clone.wiki">fossil clone</a> URL FILENAME    <a href="#tof">&#7547;</a>
   190         -
          181  +<hr><a href="#tof">&#710;</a>
          182  +    <a name="clone">Usage: </a><a href="cmd_clone.wiki">fossil clone</a> URL FILENAME
   191    183       Make a clone of a repository specified by URL in the local
   192    184       file named FILENAME.
   193    185   
   194         -
   195         -    <a name="close">Usage: </a><a href="cmd_close.wiki">fossil close</a> ?-f|--force?    <a href="#tof">&#7547;</a>
   196         -
          186  +<hr><a href="#tof">&#710;</a>
          187  +    <a name="close">Usage: </a><a href="cmd_close.wiki">fossil close</a> ?-f|--force?
   197    188       The opposite of "open".  Close the current database connection.
   198    189       Require a -f or --force flag if there are unsaved changed in the
   199    190       current check-out.
   200    191   
   201         -
   202         -    <a name="configure">Usage: </a><a href="cmd_configure.wiki">fossil configure</a> METHOD ...    <a href="#tof">&#7547;</a>
   203         -
          192  +<hr><a href="#tof">&#710;</a>
          193  +    <a name="configure">Usage: </a><a href="cmd_configure.wiki">fossil configure</a> METHOD ...
   204    194       Where METHOD is one of: export import merge pull push reset.  All methods
   205    195       accept the -R or --repository option to specific a repository.
   206    196   
   207    197       fossil configuration export AREA FILENAME
   208    198   
   209    199       Write to FILENAME exported configuraton information for AREA.
   210    200       AREA can be one of:  all ticket skin project
................................................................................
   220    210       the current configuration.  Existing values take priority over
   221    211       values read from FILENAME.
   222    212   
   223    213       fossil configuration pull AREA ?URL?
   224    214   
   225    215       Pull and install the configuration from a different server
   226    216       identified by URL.  If no URL is specified, then the default
   227         -    server is used. 
   228         -
          217  +    server is used.
   229    218       fossil configuration push AREA ?URL?
   230    219   
   231    220       Push the local configuration into the remote server identified
   232    221       by URL.  Admin privilege is required on the remote server for
   233    222       this to work.
   234    223   
   235    224       fossil configuration reset AREA
................................................................................
   236    225   
   237    226       Restore the configuration to the default.  AREA as above.
   238    227   
   239    228       WARNING: Do not import, merge, or pull configurations from an untrusted
   240    229       source.  The inbound configuration is not checked for safety and can
   241    230       introduce security vulnerabilities.
   242    231   
   243         -
   244         -    COMMAND: deconstruct 
   245         -    <a name="deconstruct">Usage: </a><a href="cmd_deconstruct.wiki">fossil deconstruct</a> ?-R|--repository REPOSITORY? DESTINATION    <a href="#tof">&#7547;</a>
   246         -
          232  +<hr><a href="#tof">&#710;</a>
          233  +    COMMAND: deconstruct
          234  +    <a name="deconstruct">Usage: </a><a href="cmd_deconstruct.wiki">fossil deconstruct</a> ?-R|--repository REPOSITORY? DESTINATION
   247    235       Populates the indicated DESTINATION directory with copies of all
   248    236       artifcats contained within the repository.  Artifacts are named AA/bbbbb
   249    237       where AA is the first 2 characters of the artifact ID and bbbbb is the
   250    238       remaining 38 characters.
   251    239   
   252         -
   253         -    <a name="rm">Usage: </a><a href="cmd_rm.wiki">fossil rm</a> FILE...    <a href="#tof">&#7547;</a>
   254         -    or: fossil del FILE...
          240  +<hr><a href="#tof">&#710;</a>
          241  +    <a name="rm">Usage: </a><a href="cmd_rm.wiki">fossil rm</a> FILE...    or: fossil del FILE...
   255    242       Remove one or more files from the tree.
   256    243   
   257         -
   258         -    <a name="descendants">Usage: </a><a href="cmd_descendants.wiki">fossil descendants</a> ?BASELINE-ID?    <a href="#tof">&#7547;</a>
   259         -
          244  +<hr><a href="#tof">&#710;</a>
          245  +    <a name="descendants">Usage: </a><a href="cmd_descendants.wiki">fossil descendants</a> ?BASELINE-ID?
   260    246       Find all leaf descendants of the baseline specified or if the argument
   261    247       is omitted, of the baseline currently checked out.
   262    248   
   263         -
   264         -    <a name="diff">Usage: </a><a href="cmd_diff.wiki">fossil diff</a>|gdiff ?-i? ?-r REVISION? FILE...    <a href="#tof">&#7547;</a>
   265         -
          249  +<hr><a href="#tof">&#710;</a>
          250  +    <a name="diff">Usage: </a><a href="cmd_diff.wiki">fossil diff</a>|gdiff ?-i? ?-r REVISION? FILE...
   266    251       Show the difference between the current version of a file (as it
   267    252       exists on disk) and that same file as it was checked out.
   268    253   
   269    254       diff will show a textual diff while gdiff will attempt to run a
   270    255       graphical diff command that you have setup. If the choosen command
   271    256       is not yet configured, the internal textual diff command will be
   272    257       used.
................................................................................
   281    266       fossil setting gdiff-command tkdiff
   282    267       fossil setting gdiff-command eskill22
   283    268       fossil setting gdiff-command tortoisemerge
   284    269       fossil setting gdiff-command meld
   285    270       fossil setting gdiff-command xxdiff
   286    271       fossil setting gdiff-command kdiff3
   287    272   
   288         -
   289         -    <a name="extra">Usage: </a><a href="cmd_extra.wiki">fossil extra</a>    <a href="#tof">&#7547;</a>
   290         -
          273  +<hr><a href="#tof">&#710;</a>
          274  +    <a name="extra">Usage: </a><a href="cmd_extra.wiki">fossil extra</a>
   291    275       Print a list of all files in the source tree that are not part of
   292    276       the current checkout.  See also the "clean" command.
   293    277   
   294         -
   295         -    <a name="help">Usage: </a><a href="cmd_help.wiki">fossil help</a> COMMAND    <a href="#tof">&#7547;</a>
   296         -
          278  +<hr><a href="#tof">&#710;</a>
          279  +    <a name="help">Usage: </a><a href="cmd_help.wiki">fossil help</a> COMMAND
   297    280       Display information on how to use COMMAND
   298    281   
   299         -
   300         -    <a name="http">Usage: </a><a href="cmd_http.wiki">fossil http</a> REPOSITORY    <a href="#tof">&#7547;</a>
   301         -
          282  +<hr><a href="#tof">&#710;</a>
          283  +    <a name="http">Usage: </a><a href="cmd_http.wiki">fossil http</a> REPOSITORY
   302    284       Handle a single HTTP request appearing on stdin.  The resulting webpage
   303    285       is delivered on stdout.  This method is used to launch an HTTP request
   304         -    handler from inetd, for example.  The argument is the name of the 
   305         -    repository.
          286  +    handler from inetd, for example.  The argument is the name of the    repository.
   306    287   
   307         -
   308         -    <a name="info">Usage: </a><a href="cmd_info.wiki">fossil info</a> ?ARTIFACT-ID|FILENAME?    <a href="#tof">&#7547;</a>
   309         -
          288  +<hr><a href="#tof">&#710;</a>
          289  +    <a name="info">Usage: </a><a href="cmd_info.wiki">fossil info</a> ?ARTIFACT-ID|FILENAME?
   310    290       With no arguments, provide information about the current tree.
   311    291       If an argument is specified, provide information about the object
   312    292       in the respository of the current tree that the argument refers
   313    293       to.  Or if the argument is the name of a repository, show
   314    294       information about that repository.
   315    295   
   316         -
   317         -    <a name="leaves">Usage: </a><a href="cmd_leaves.wiki">fossil leaves</a>    <a href="#tof">&#7547;</a>
   318         -
          296  +<hr><a href="#tof">&#710;</a>
          297  +    <a name="leaves">Usage: </a><a href="cmd_leaves.wiki">fossil leaves</a>
   319    298       Find leaves of all branches.
   320    299   
   321         -
   322         -    <a name="ls">Usage: </a><a href="cmd_ls.wiki">fossil ls</a>    <a href="#tof">&#7547;</a>
   323         -
          300  +<hr><a href="#tof">&#710;</a>
          301  +    <a name="ls">Usage: </a><a href="cmd_ls.wiki">fossil ls</a>
   324    302       Show the names of all files in the current checkout
   325    303   
   326         -
   327         -    <a name="merge">Usage: </a><a href="cmd_merge.wiki">fossil merge</a> VERSION    <a href="#tof">&#7547;</a>
   328         -
          304  +<hr><a href="#tof">&#710;</a>
          305  +    <a name="merge">Usage: </a><a href="cmd_merge.wiki">fossil merge</a> VERSION
   329    306       The argument is a version that should be merged into the current
   330         -    checkout. 
   331         -
          307  +    checkout.
   332    308       Only file content is merged.  The result continues to use the
   333    309       file and directory names from the current check-out even if those
   334    310       names might have been changed in the branch being merged in.
   335    311   
   336         -
   337         -    <a name="mv">Usage: </a><a href="cmd_mv.wiki">fossil mv|rename</a> OLDNAME NEWNAME    <a href="#tof">&#7547;</a>
   338         -       or: fossil mv|rename OLDNAME... DIR
          312  +<hr><a href="#tof">&#710;</a>
          313  +    <a name="mv">Usage: </a><a href="cmd_mv.wiki">fossil mv|rename</a> OLDNAME NEWNAME       or: fossil mv|rename OLDNAME... DIR
   339    314   
   340    315       Move or rename one or more files within the tree
   341    316   
   342    317       This command does not rename the files on disk.  All this command does is
   343    318       record the fact that filenames have changed so that appropriate notations
   344    319       can be made at the next commit/checkin.
   345         -
          320  +<hr><a href="#tof">&#710;</a>
   346    321       <a name="new">Usage: </a><a href="cmd_new.wiki">fossil new</a> FILENAME
   347    322   
   348    323       Create a repository for a new project in the file named FILENAME.
   349    324       This command is distinct from "clone".  The "clone" command makes
   350    325       a copy of an existing project.  This command starts a new project.
   351    326   
   352         -
   353         -    <a name="open">Usage: </a><a href="cmd_open.wiki">fossil open</a> FILENAME    <a href="#tof">&#7547;</a>
   354         -
          327  +<hr><a href="#tof">&#710;</a>
          328  +    <a name="open">Usage: </a><a href="cmd_open.wiki">fossil open</a> FILENAME
   355    329       Open a connection to the local repository in FILENAME.  A checkout
   356    330       for the repository is created with its root at the working directory.
   357    331       See also the "close" command.
   358    332   
   359         -
   360         -    <a name="pull">Usage: </a><a href="cmd_pull.wiki">fossil pull</a> ?URL? ?-R|--respository REPOSITORY?    <a href="#tof">&#7547;</a>
   361         -
          333  +<hr><a href="#tof">&#710;</a>
          334  +    <a name="pull">Usage: </a><a href="cmd_pull.wiki">fossil pull</a> ?URL? ?-R|--respository REPOSITORY?
   362    335       Pull changes in a remote repository into the local repository.
   363    336       The repository is identified by the -R or --repository option.
   364    337       If there is no such option then the open repository is used.
   365    338       The URL of the remote server is specified on the command line
   366    339       If no URL is specified then the URL used by the most recent
   367    340       "pull", "push", or "sync" command is used.
   368    341   
................................................................................
   372    345   
   373    346       The "USER@" and ":PORT" substrings are optional.
   374    347       The "USER" substring specifies the login user.  You will be
   375    348       prompted for the password on the command-line.  The PORT
   376    349       specifies the TCP port of the server.  The default port is
   377    350       80.
   378    351   
   379         -
   380         -    <a name="push">Usage: </a><a href="cmd_push.wiki">fossil push</a> ?URL? ?-R|--repository REPOSITORY?    <a href="#tof">&#7547;</a>
   381         -
          352  +<hr><a href="#tof">&#710;</a>
          353  +    <a name="push">Usage: </a><a href="cmd_push.wiki">fossil push</a> ?URL? ?-R|--repository REPOSITORY?
   382    354       Push changes in the local repository over into a remote repository.
   383    355       See the "pull" command for additional information.
   384         -
   385         -    <a name="rebuild">Usage: </a><a href="cmd_rebuild.wiki">fossil rebuild</a> REPOSITORY    <a href="#tof">&#7547;</a>
   386         -
          356  +<hr><a href="#tof">&#710;</a>
          357  +    <a name="rebuild">Usage: </a><a href="cmd_rebuild.wiki">fossil rebuild</a> REPOSITORY
   387    358       Reconstruct the named repository database from the core
   388    359       records.  Run this command after updating the fossil
   389    360       executable in a way that changes the database schema.
   390    361   
   391         -
   392         -    COMMAND: reconstruct 
   393         -    <a name="reconstruct">Usage: </a><a href="cmd_reconstruct.wiki">fossil reconstruct</a> REPOSITORY ORIGIN    <a href="#tof">&#7547;</a>
   394         -
          362  +<hr><a href="#tof">&#710;</a>
          363  +    COMMAND: reconstruct
          364  +    <a name="reconstruct">Usage: </a><a href="cmd_reconstruct.wiki">fossil reconstruct</a> REPOSITORY ORIGIN
   395    365       Creates the REPOSITORY and populates it with the artifacts in the
   396    366       indicated ORIGIN directory.
   397    367   
   398         -
   399         -    <a name="redo">Usage: </a><a href="cmd_redo.wiki">fossil redo</a> ?FILENAME...?    <a href="#tof">&#7547;</a>
   400         -
          368  +<hr><a href="#tof">&#710;</a>
          369  +    <a name="redo">Usage: </a><a href="cmd_redo.wiki">fossil redo</a> ?FILENAME...?
   401    370       Redo the an update or merge operation that has been undone by the
   402    371       undo command.  If FILENAME is specified then restore the changes
   403    372       associated with the named file(s) but otherwise leave the update
   404    373       or merge undone.
   405    374   
   406    375       A single level of undo/redo is supported.  The undo/redo stack
   407    376       is cleared by the commit and checkout commands.
   408    377   
   409         -
   410         -    <a name="revert">Usage: </a><a href="cmd_revert.wiki">fossil revert</a> ?--yes? ?-r REVISION? FILE    <a href="#tof">&#7547;</a>
   411         -
          378  +<hr><a href="#tof">&#710;</a>
          379  +    <a name="revert">Usage: </a><a href="cmd_revert.wiki">fossil revert</a> ?--yes? ?-r REVISION? FILE
   412    380       Revert to the current repository version of FILE, or to
   413    381       the version associated with baseline REVISION if the -r flag
   414    382       appears.  This command will confirm your operation unless the
   415    383       file is missing or the --yes option is used.
   416    384   
   417         -
   418         -    <a name="server">Usage: </a><a href="cmd_server.wiki">fossil server</a> ?-P|--port TCPPORT? ?REPOSITORY?    <a href="#tof">&#7547;</a>
   419         -    Or: fossil ui ?-P|--port TCPPORT? ?REPOSITORY?
          385  +<hr><a href="#tof">&#710;</a>
          386  +    <a name="server">Usage: </a><a href="cmd_server.wiki">fossil server</a> ?-P|--port TCPPORT? ?REPOSITORY?    Or: fossil ui ?-P|--port TCPPORT? ?REPOSITORY?
   420    387   
   421    388       Open a socket and begin listening and responding to HTTP requests on
   422    389       TCP port 8080, or on any other TCP port defined by the -P or
   423    390       --port option.  The optional argument is the name of the repository.
   424    391       The repository argument may be omitted if the working directory is
   425    392       within an open checkout.
   426    393   
   427    394       The "ui" command automatically starts a web browser after initializing
   428    395       the web server.
   429    396   
   430         -
          397  +<hr><a href="#tof">&#710;</a>
   431    398       COMMAND: settings
   432    399       COMMAND: unset
   433         -    <a name="setting">Usage: </a><a href="cmd_setting.wiki">fossil setting</a> ?PROPERTY? ?VALUE? ?-global?    <a href="#tof">&#7547;</a>
   434         -    fossil unset PROPERTY ?-global?
          400  +    <a name="setting">Usage: </a><a href="cmd_setting.wiki">fossil setting</a> ?PROPERTY? ?VALUE? ?-global?    fossil unset PROPERTY ?-global?
   435    401   
   436    402       The "setting" command with no arguments lists all properties and their
   437    403       values.  With just a property name it shows the value of that property.
   438    404       With a value argument it changes the property for the current repository.
   439    405   
   440    406       The "unset" command clears a property setting.
   441    407   
................................................................................
   469    435       then a direct HTTP connection is used.
   470    436   
   471    437       web-browser      A shell command used to launch your preferred
   472    438       web browser when given a URL as an argument.
   473    439       Defaults to "start" on windows, "open" on Mac,
   474    440       and "firefox" on Unix.
   475    441   
   476         -
   477         -    <a name="status">Usage: </a><a href="cmd_status.wiki">fossil status</a>    <a href="#tof">&#7547;</a>
   478         -
          442  +<hr><a href="#tof">&#710;</a>
          443  +    <a name="status">Usage: </a><a href="cmd_status.wiki">fossil status</a>
   479    444       Report on the status of the current checkout.
   480    445   
   481         -
   482         -    <a name="sync">Usage: </a><a href="cmd_sync.wiki">fossil sync</a> ?URL? ?-R|--repository REPOSITORY?    <a href="#tof">&#7547;</a>
   483         -
          446  +<hr><a href="#tof">&#710;</a>
          447  +    <a name="sync">Usage: </a><a href="cmd_sync.wiki">fossil sync</a> ?URL? ?-R|--repository REPOSITORY?
   484    448       Synchronize the local repository with a remote repository.  This is
   485    449       the equivalent of running both "push" and "pull" at the same time.
   486    450       See the "pull" command for additional information.
   487    451   
   488         -
   489         -    <a name="tag">Usage: </a><a href="cmd_tag.wiki">fossil tag</a> SUBCOMMAND ...    <a href="#tof">&#7547;</a>
   490         -
          452  +<hr><a href="#tof">&#710;</a>
          453  +    <a name="tag">Usage: </a><a href="cmd_tag.wiki">fossil tag</a> SUBCOMMAND ...
   491    454       Run various subcommands to control tags and properties
   492    455   
   493    456       fossil tag add ?--raw? TAGNAME BASELINE ?VALUE?
   494    457   
   495    458       Add a new tag or property to BASELINE. The tag will
   496    459       be usable instead of a BASELINE in commands such as
   497    460       update and merge.
................................................................................
   538    501       will be taken as an artifact or baseline ID and fossil will
   539    502       probably complain that no such revision was found. However
   540    503   
   541    504       fossil update tag:decaf
   542    505   
   543    506       will assume that "decaf" is a tag/branch name.
   544    507   
   545         -
   546         -    <a name="timeline">Usage: </a><a href="cmd_timeline.wiki">fossil timeline</a> ?WHEN? ?BASELINE|DATETIME? ?-n|--count N?    <a href="#tof">&#7547;</a>
   547         -
          508  +<hr><a href="#tof">&#710;</a>
          509  +    <a name="timeline">Usage: </a><a href="cmd_timeline.wiki">fossil timeline</a> ?WHEN? ?BASELINE|DATETIME? ?-n|--count N?
   548    510       Print a summary of activity going backwards in date and time
   549    511       specified or from the current date and time if no arguments
   550    512       are given.  Show as many as N (default 20) check-ins.  The
   551    513       WHEN argument can be any unique abbreviation of one of these
   552    514       keywords:
   553    515   
   554    516       before
................................................................................
   557    519       ancestors | parents
   558    520   
   559    521       The BASELINE can be any unique prefix of 4 characters or more.
   560    522       The DATETIME should be in the ISO8601 format.  For
   561    523       examples: "2007-08-18 07:21:21".  You can also say "current"
   562    524       for the current version or "now" for the current time.
   563    525   
   564         -
   565         -    <a name="undo">Usage: </a><a href="cmd_undo.wiki">fossil undo</a> ?FILENAME...?    <a href="#tof">&#7547;</a>
   566         -
          526  +<hr><a href="#tof">&#710;</a>
          527  +    <a name="undo">Usage: </a><a href="cmd_undo.wiki">fossil undo</a> ?FILENAME...?
   567    528       Undo the most recent update or merge operation.  If FILENAME is
   568    529       specified then restore the content of the named file(s) but otherwise
   569    530       leave the update or merge in effect.
   570    531   
   571    532       A single level of undo/redo is supported.  The undo/redo stack
   572    533       is cleared by the commit and checkout commands.
   573    534   
   574         -
   575         -    <a name="update">Usage: </a><a href="cmd_update.wiki">fossil update</a> ?VERSION? ?--latest?    <a href="#tof">&#7547;</a>
   576         -
          535  +<hr><a href="#tof">&#710;</a>
          536  +    <a name="update">Usage: </a><a href="cmd_update.wiki">fossil update</a> ?VERSION? ?--latest?
   577    537       The optional argument is a version that should become the current
   578    538       version.  If the argument is omitted, then use the leaf of the
   579         -    tree that begins with the current version, if there is only a 
   580         -    single leaf.  If there are a multiple leaves, the latest is used
          539  +    tree that begins with the current version, if there is only a    single leaf.  If there are a multiple leaves, the latest is used
   581    540       if the --latest flag is present.
   582    541   
   583    542       This command is different from the "checkout" in that edits are
   584    543       not overwritten.  Edits are merged into the new version.
   585    544   
   586         -
   587         -    <a name="user">Usage: </a><a href="cmd_user.wiki">fossil user</a> SUBCOMMAND ...  ?-R|--repository FILE?    <a href="#tof">&#7547;</a>
   588         -
          545  +<hr><a href="#tof">&#710;</a>
          546  +    <a name="user">Usage: </a><a href="cmd_user.wiki">fossil user</a> SUBCOMMAND ...  ?-R|--repository FILE?
   589    547       Run various subcommands on users of the open repository or of
   590    548       the repository identified by the -R or --repository option.
   591    549   
   592    550       fossil user capabilities USERNAME ?STRING?
   593    551   
   594    552       Query or set the capabilities for user USERNAME
   595    553   
................................................................................
   608    566       deleted.  They can be denied all access but they must continue
   609    567       to exist in the database.
   610    568   
   611    569       fossil user password USERNAME
   612    570   
   613    571       Change the web access password for a user.
   614    572   
   615         -
   616         -    <a name="version">Usage: </a><a href="cmd_version.wiki">fossil version</a>    <a href="#tof">&#7547;</a>
   617         -
          573  +<hr><a href="#tof">&#710;</a>
          574  +    <a name="version">Usage: </a><a href="cmd_version.wiki">fossil version</a>
   618    575       Print the source code version number for the fossil executable.
   619    576   
   620         -
   621         -    <a name="wiki">Usage: </a><a href="cmd_wiki.wiki">fossil wiki</a> (export|create|commit|list) WikiName    <a href="#tof">&#7547;</a>
   622         -
          577  +<hr><a href="#tof">&#710;</a>
          578  +    <a name="wiki">Usage: </a><a href="cmd_wiki.wiki">fossil wiki</a> (export|create|commit|list) WikiName
   623    579       Run various subcommands to fetch wiki entries.
   624    580   
   625    581       fossil wiki export PAGENAME ?FILE?
   626    582   
   627    583       Sends the latest version of the PAGENAME wiki
   628    584       entry to the given file or standard output.
   629    585   
................................................................................
   660    616       fossil wiki diff ?ARTIFACT? ?-f infile[=stdin]? EntryName
   661    617   
   662    618       Diffs the local copy of a page with a given version (defaulting
   663    619       to the head version).
   664    620   
   665    621     </pre></nowiki>
   666    622   
   667         -  <hr>
          623  +  <hr><a href="#tof">&#710;</a>
   668    624   
   669    625       <h3>Caveats</h3>
   670    626       This is not actually a reference, it's the start of a reference.
   671    627       There are wikilinks to uncreated pages for the commands.  This was
   672    628       created by running the fossil help for each command listed by running
   673    629       fossil help...  Duplicate commands are only listed once (I
   674    630       <i>think</i>).  There are several bits of <b>fossil</b> that are not addressed
   675    631       in the help for commands (special wiki directories, special users, etc.)
   676    632       so they are (currently) not addressed here.  Clarity and brevity may be
   677    633       sacrificed for expediency at the authors indiscretion.  All spelling and
   678    634       grammatical mistakes are somebody elses fault.<code>  void * </code>
   679    635       prohibited where<code> __C_PLUS_PLUS__ </code>. Title and taxes extra.
   680    636       Not valid in Hooptigonia.
   681         -<a href="#tof">&#7547;</a>