Fossil

Check-in [f8f8baf9]
Login

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

Overview
Comment:Add link to branching page.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1:f8f8baf945fb4187cefc19ecc3f68a0aaa0b1912
User & Date: kejoki 2009-01-29 19:11:52
Context
2009-01-30
21:18
Changed update docs, ** ADDED A _SPECIAL_ (but MUTYPE_BLOCK) wikitag <annotation> to put html comments in wikimarkup Leaf check-in: 51868cb1 user: kkennell tags: kkinnell-exp
2009-01-29
23:04
Merge in kkinnell's documentation updates. check-in: 24c045f3 user: drh tags: trunk
19:11
Add link to branching page. check-in: f8f8baf9 user: kejoki tags: trunk
2009-01-23
21:24
First draft of the "branching" document. check-in: 2e275c14 user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/reference.wiki.

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
...
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213

  * 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&#8212;the 'clone'
  command&#8212;unambiguous.

  * Pragmatically, a <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 string, or a
  <code>tag</code>.</em>






  You should probably start interacting with fossil at the command
  line by asking it what it can
  do:&nbsp;&nbsp;&nbsp;&nbsp;<a name="tof">&#710;</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>
	<td><a href="#configure">configuration</a></td>
	<td><a href="#leaves">leaves</a></td>
	<td><a href="#redo">redo</a></td>
	<td><a href="#timeline">timeline</a></td>
      </tr>
      <tr>
	<td><a href="#all">all</a>*</td>
	<td><a href="#deconstruct">deconstruct</a></td>
................................................................................
<hr><a href="#tof">&#710;</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">&#710;</a>
    <a name="configure">Usage: </a><a href="cmd_configure.wiki">fossil configure</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.
    AREA can be one of:  all ticket skin project







|






>
>
>
>
>











|







 







|







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
...
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218

  * 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&#8212;the 'clone'
  command&#8212;unambiguous.

  * Pragmatically, a [ | <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 string, or a
  <code>tag</code>.</em>

  * SCM in a distributed environment can be a bit confusing with
  regard to branching, merging, and versions in general.  See the
  [./branching.wiki | explanation of branching] and it will all make
  much more sense.

  You should probably start interacting with fossil at the command
  line by asking it what it can
  do:&nbsp;&nbsp;&nbsp;&nbsp;<a name="tof">&#710;</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>
	<td><a href="#configuration">configuration</a></td>
	<td><a href="#leaves">leaves</a></td>
	<td><a href="#redo">redo</a></td>
	<td><a href="#timeline">timeline</a></td>
      </tr>
      <tr>
	<td><a href="#all">all</a>*</td>
	<td><a href="#deconstruct">deconstruct</a></td>
................................................................................
<hr><a href="#tof">&#710;</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">&#710;</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.
    AREA can be one of:  all ticket skin project