Fossil SCM
Converted obsolete <a name> anchors in the quickstart doc to fragment identifiers on the headers, and added fragment IDs to all of the h2 level headers that lacked one.
Commit
8da7b15e7149d39a367e0f65fbf0e3517a21d06a0ea2be4198217a84227a39e8
Parent
aae387d956850ab…
1 file changed
+11
-13
+11
-13
| --- www/quickstart.wiki | ||
| +++ www/quickstart.wiki | ||
| @@ -12,12 +12,11 @@ | ||
| 12 | 12 | binary</a> |
| 13 | 13 | or <a href="build.wiki">compile it yourself</a> from sources. |
| 14 | 14 | Install Fossil by putting the fossil binary |
| 15 | 15 | someplace on your $PATH.</p> |
| 16 | 16 | |
| 17 | -<a name="fslclone"></a> | |
| 18 | -<h2>General Work Flow</h2> | |
| 17 | +<h2 id="workflow" name="fslclone">General Work Flow</h2> | |
| 19 | 18 | |
| 20 | 19 | <p>Fossil works with repository files (a database with the project's |
| 21 | 20 | complete history) and with checked-out local trees (the working directory |
| 22 | 21 | you use to do your work). |
| 23 | 22 | (See [./whyusefossil.wiki#definitions | definitions] for more background.) |
| @@ -32,20 +31,20 @@ | ||
| 32 | 31 | </ul> |
| 33 | 32 | |
| 34 | 33 | <p>The following sections will give you a brief overview of these |
| 35 | 34 | operations.</p> |
| 36 | 35 | |
| 37 | -<h2>Starting A New Project</h2> | |
| 36 | +<h2 id="new">Starting A New Project</h2> | |
| 38 | 37 | |
| 39 | 38 | <p>To start a new project with fossil, create a new empty repository |
| 40 | 39 | this way: ([/help/init | more info]) </p> |
| 41 | 40 | |
| 42 | 41 | <blockquote> |
| 43 | 42 | <b>fossil init </b><i> repository-filename</i> |
| 44 | 43 | </blockquote> |
| 45 | 44 | |
| 46 | -<h2>Cloning An Existing Repository</h2> | |
| 45 | +<h2 id="clone">Cloning An Existing Repository</h2> | |
| 47 | 46 | |
| 48 | 47 | <p>Most fossil operations interact with a repository that is on the |
| 49 | 48 | local disk drive, not on a remote system. Hence, before accessing |
| 50 | 49 | a remote repository it is necessary to make a local copy of that |
| 51 | 50 | repository. Making a local copy of a remote repository is called |
| @@ -88,18 +87,18 @@ | ||
| 88 | 87 | sensitive information such as password hashes and email addresses. If you |
| 89 | 88 | want to share Fossil repositories directly, consider running the |
| 90 | 89 | [/help/scrub|fossil scrub] command to remove sensitive information |
| 91 | 90 | before transmitting the file. |
| 92 | 91 | |
| 93 | -<h2>Importing From Another Version Control System</h2> | |
| 92 | +<h2 id="import">Importing From Another Version Control System</h2> | |
| 94 | 93 | |
| 95 | 94 | <p>Rather than start a new project, or clone an existing Fossil project, |
| 96 | 95 | you might prefer to |
| 97 | 96 | <a href="./inout.wiki">import an existing Git project</a> |
| 98 | 97 | into Fossil using the [/help/import | fossil import] command. |
| 99 | 98 | |
| 100 | -<h2>Checking Out A Local Tree</h2> | |
| 99 | +<h2 id="checkout">Checking Out A Local Tree</h2> | |
| 101 | 100 | |
| 102 | 101 | <p>To work on a project in fossil, you need to check out a local |
| 103 | 102 | copy of the source tree. Create the directory you want to be |
| 104 | 103 | the root of your tree and cd into that directory. Then |
| 105 | 104 | do this: ([/help/open | more info])</p> |
| @@ -141,11 +140,11 @@ | ||
| 141 | 140 | does a "soft" switch, merging any local changes into the target |
| 142 | 141 | version, whereas [/help/checkout | checkout] does not |
| 143 | 142 | automatically sync and does a "hard" switch, overwriting local |
| 144 | 143 | changes if told to do so.</p> |
| 145 | 144 | |
| 146 | -<h2>Configuring Your Local Repository</h2> | |
| 145 | +<h2 id="config">Configuring Your Local Repository</h2> | |
| 147 | 146 | |
| 148 | 147 | <p>When you create a new repository, either by cloning an existing |
| 149 | 148 | project or create a new project of your own, you usually want to do some |
| 150 | 149 | local configuration. This is easily accomplished using the web-server |
| 151 | 150 | that is built into fossil. Start the fossil web server like this: |
| @@ -173,11 +172,11 @@ | ||
| 173 | 172 | should, change this after you create a few users.</p> |
| 174 | 173 | |
| 175 | 174 | <p>When you are finished configuring, just press Control-C or use |
| 176 | 175 | the <b>kill</b> command to shut down the mini-server.</p> |
| 177 | 176 | |
| 178 | -<h2>Making Changes</h2> | |
| 177 | +<h2 id="changes">Making Changes</h2> | |
| 179 | 178 | |
| 180 | 179 | <p>To add new files to your project, or remove old files, use these |
| 181 | 180 | commands:</p> |
| 182 | 181 | |
| 183 | 182 | <blockquote> |
| @@ -201,11 +200,11 @@ | ||
| 201 | 200 | feature can be disabled. (More information about |
| 202 | 201 | [./concepts.wiki#workflow|autosync] and how to disable it.) |
| 203 | 202 | Remember that your coworkers can not see your changes until you |
| 204 | 203 | commit and push them.</p> |
| 205 | 204 | |
| 206 | -<h2>Sharing Changes</h2> | |
| 205 | +<h2 id="sharing">Sharing Changes</h2> | |
| 207 | 206 | |
| 208 | 207 | <p>When [./concepts.wiki#workflow|autosync] is turned off, |
| 209 | 208 | the changes you [/help/commit | commit] are only |
| 210 | 209 | on your local repository. |
| 211 | 210 | To share those changes with other repositories, do:</p> |
| @@ -257,11 +256,11 @@ | ||
| 257 | 256 | <p>Is similar to update except that it does not honor the autosync |
| 258 | 257 | setting, nor does it merge in local changes - it prefers to overwrite |
| 259 | 258 | them and fails if local changes exist unless the <tt>--force</tt> |
| 260 | 259 | flag is used.</p> |
| 261 | 260 | |
| 262 | -<h2>Branching And Merging</h2> | |
| 261 | +<h2 id="branch" name="merge">Branching And Merging</h2> | |
| 263 | 262 | |
| 264 | 263 | <p>Use the --branch option to the [/help/commit | commit] command |
| 265 | 264 | to start a new branch. Note that in Fossil, branches are normally |
| 266 | 265 | created when you commit, not before you start editing. You can |
| 267 | 266 | use the [/help/branch | branch new] command to create a new branch |
| @@ -315,11 +314,11 @@ | ||
| 315 | 314 | mistake. Undo and redo only work for changes that have |
| 316 | 315 | not yet been checked in using commit and there is only a single |
| 317 | 316 | level of undo/redo.</p> |
| 318 | 317 | |
| 319 | 318 | |
| 320 | -<h2>Setting Up A Server</h2> | |
| 319 | +<h2 id="server">Setting Up A Server</h2> | |
| 321 | 320 | |
| 322 | 321 | <p>Fossil can act as a stand-alone web server using one of these |
| 323 | 322 | commands:</p> |
| 324 | 323 | |
| 325 | 324 | <blockquote> |
| @@ -347,12 +346,11 @@ | ||
| 347 | 346 | </ul> |
| 348 | 347 | |
| 349 | 348 | <p>The [./selfhost.wiki | self-hosting fossil repositories] use |
| 350 | 349 | CGI. |
| 351 | 350 | |
| 352 | -<a name="proxy"></a> | |
| 353 | -<h2>HTTP Proxies</h2> | |
| 351 | +<h2 id="proxy">HTTP Proxies</h2> | |
| 354 | 352 | |
| 355 | 353 | <p>If you are behind a restrictive firewall that requires you to use |
| 356 | 354 | an HTTP proxy to reach the internet, then you can configure the proxy |
| 357 | 355 | in three different ways. You can tell fossil about your proxy using |
| 358 | 356 | a command-line option on commands that use the network, |
| 359 | 357 |
| --- www/quickstart.wiki | |
| +++ www/quickstart.wiki | |
| @@ -12,12 +12,11 @@ | |
| 12 | binary</a> |
| 13 | or <a href="build.wiki">compile it yourself</a> from sources. |
| 14 | Install Fossil by putting the fossil binary |
| 15 | someplace on your $PATH.</p> |
| 16 | |
| 17 | <a name="fslclone"></a> |
| 18 | <h2>General Work Flow</h2> |
| 19 | |
| 20 | <p>Fossil works with repository files (a database with the project's |
| 21 | complete history) and with checked-out local trees (the working directory |
| 22 | you use to do your work). |
| 23 | (See [./whyusefossil.wiki#definitions | definitions] for more background.) |
| @@ -32,20 +31,20 @@ | |
| 32 | </ul> |
| 33 | |
| 34 | <p>The following sections will give you a brief overview of these |
| 35 | operations.</p> |
| 36 | |
| 37 | <h2>Starting A New Project</h2> |
| 38 | |
| 39 | <p>To start a new project with fossil, create a new empty repository |
| 40 | this way: ([/help/init | more info]) </p> |
| 41 | |
| 42 | <blockquote> |
| 43 | <b>fossil init </b><i> repository-filename</i> |
| 44 | </blockquote> |
| 45 | |
| 46 | <h2>Cloning An Existing Repository</h2> |
| 47 | |
| 48 | <p>Most fossil operations interact with a repository that is on the |
| 49 | local disk drive, not on a remote system. Hence, before accessing |
| 50 | a remote repository it is necessary to make a local copy of that |
| 51 | repository. Making a local copy of a remote repository is called |
| @@ -88,18 +87,18 @@ | |
| 88 | sensitive information such as password hashes and email addresses. If you |
| 89 | want to share Fossil repositories directly, consider running the |
| 90 | [/help/scrub|fossil scrub] command to remove sensitive information |
| 91 | before transmitting the file. |
| 92 | |
| 93 | <h2>Importing From Another Version Control System</h2> |
| 94 | |
| 95 | <p>Rather than start a new project, or clone an existing Fossil project, |
| 96 | you might prefer to |
| 97 | <a href="./inout.wiki">import an existing Git project</a> |
| 98 | into Fossil using the [/help/import | fossil import] command. |
| 99 | |
| 100 | <h2>Checking Out A Local Tree</h2> |
| 101 | |
| 102 | <p>To work on a project in fossil, you need to check out a local |
| 103 | copy of the source tree. Create the directory you want to be |
| 104 | the root of your tree and cd into that directory. Then |
| 105 | do this: ([/help/open | more info])</p> |
| @@ -141,11 +140,11 @@ | |
| 141 | does a "soft" switch, merging any local changes into the target |
| 142 | version, whereas [/help/checkout | checkout] does not |
| 143 | automatically sync and does a "hard" switch, overwriting local |
| 144 | changes if told to do so.</p> |
| 145 | |
| 146 | <h2>Configuring Your Local Repository</h2> |
| 147 | |
| 148 | <p>When you create a new repository, either by cloning an existing |
| 149 | project or create a new project of your own, you usually want to do some |
| 150 | local configuration. This is easily accomplished using the web-server |
| 151 | that is built into fossil. Start the fossil web server like this: |
| @@ -173,11 +172,11 @@ | |
| 173 | should, change this after you create a few users.</p> |
| 174 | |
| 175 | <p>When you are finished configuring, just press Control-C or use |
| 176 | the <b>kill</b> command to shut down the mini-server.</p> |
| 177 | |
| 178 | <h2>Making Changes</h2> |
| 179 | |
| 180 | <p>To add new files to your project, or remove old files, use these |
| 181 | commands:</p> |
| 182 | |
| 183 | <blockquote> |
| @@ -201,11 +200,11 @@ | |
| 201 | feature can be disabled. (More information about |
| 202 | [./concepts.wiki#workflow|autosync] and how to disable it.) |
| 203 | Remember that your coworkers can not see your changes until you |
| 204 | commit and push them.</p> |
| 205 | |
| 206 | <h2>Sharing Changes</h2> |
| 207 | |
| 208 | <p>When [./concepts.wiki#workflow|autosync] is turned off, |
| 209 | the changes you [/help/commit | commit] are only |
| 210 | on your local repository. |
| 211 | To share those changes with other repositories, do:</p> |
| @@ -257,11 +256,11 @@ | |
| 257 | <p>Is similar to update except that it does not honor the autosync |
| 258 | setting, nor does it merge in local changes - it prefers to overwrite |
| 259 | them and fails if local changes exist unless the <tt>--force</tt> |
| 260 | flag is used.</p> |
| 261 | |
| 262 | <h2>Branching And Merging</h2> |
| 263 | |
| 264 | <p>Use the --branch option to the [/help/commit | commit] command |
| 265 | to start a new branch. Note that in Fossil, branches are normally |
| 266 | created when you commit, not before you start editing. You can |
| 267 | use the [/help/branch | branch new] command to create a new branch |
| @@ -315,11 +314,11 @@ | |
| 315 | mistake. Undo and redo only work for changes that have |
| 316 | not yet been checked in using commit and there is only a single |
| 317 | level of undo/redo.</p> |
| 318 | |
| 319 | |
| 320 | <h2>Setting Up A Server</h2> |
| 321 | |
| 322 | <p>Fossil can act as a stand-alone web server using one of these |
| 323 | commands:</p> |
| 324 | |
| 325 | <blockquote> |
| @@ -347,12 +346,11 @@ | |
| 347 | </ul> |
| 348 | |
| 349 | <p>The [./selfhost.wiki | self-hosting fossil repositories] use |
| 350 | CGI. |
| 351 | |
| 352 | <a name="proxy"></a> |
| 353 | <h2>HTTP Proxies</h2> |
| 354 | |
| 355 | <p>If you are behind a restrictive firewall that requires you to use |
| 356 | an HTTP proxy to reach the internet, then you can configure the proxy |
| 357 | in three different ways. You can tell fossil about your proxy using |
| 358 | a command-line option on commands that use the network, |
| 359 |
| --- www/quickstart.wiki | |
| +++ www/quickstart.wiki | |
| @@ -12,12 +12,11 @@ | |
| 12 | binary</a> |
| 13 | or <a href="build.wiki">compile it yourself</a> from sources. |
| 14 | Install Fossil by putting the fossil binary |
| 15 | someplace on your $PATH.</p> |
| 16 | |
| 17 | <h2 id="workflow" name="fslclone">General Work Flow</h2> |
| 18 | |
| 19 | <p>Fossil works with repository files (a database with the project's |
| 20 | complete history) and with checked-out local trees (the working directory |
| 21 | you use to do your work). |
| 22 | (See [./whyusefossil.wiki#definitions | definitions] for more background.) |
| @@ -32,20 +31,20 @@ | |
| 31 | </ul> |
| 32 | |
| 33 | <p>The following sections will give you a brief overview of these |
| 34 | operations.</p> |
| 35 | |
| 36 | <h2 id="new">Starting A New Project</h2> |
| 37 | |
| 38 | <p>To start a new project with fossil, create a new empty repository |
| 39 | this way: ([/help/init | more info]) </p> |
| 40 | |
| 41 | <blockquote> |
| 42 | <b>fossil init </b><i> repository-filename</i> |
| 43 | </blockquote> |
| 44 | |
| 45 | <h2 id="clone">Cloning An Existing Repository</h2> |
| 46 | |
| 47 | <p>Most fossil operations interact with a repository that is on the |
| 48 | local disk drive, not on a remote system. Hence, before accessing |
| 49 | a remote repository it is necessary to make a local copy of that |
| 50 | repository. Making a local copy of a remote repository is called |
| @@ -88,18 +87,18 @@ | |
| 87 | sensitive information such as password hashes and email addresses. If you |
| 88 | want to share Fossil repositories directly, consider running the |
| 89 | [/help/scrub|fossil scrub] command to remove sensitive information |
| 90 | before transmitting the file. |
| 91 | |
| 92 | <h2 id="import">Importing From Another Version Control System</h2> |
| 93 | |
| 94 | <p>Rather than start a new project, or clone an existing Fossil project, |
| 95 | you might prefer to |
| 96 | <a href="./inout.wiki">import an existing Git project</a> |
| 97 | into Fossil using the [/help/import | fossil import] command. |
| 98 | |
| 99 | <h2 id="checkout">Checking Out A Local Tree</h2> |
| 100 | |
| 101 | <p>To work on a project in fossil, you need to check out a local |
| 102 | copy of the source tree. Create the directory you want to be |
| 103 | the root of your tree and cd into that directory. Then |
| 104 | do this: ([/help/open | more info])</p> |
| @@ -141,11 +140,11 @@ | |
| 140 | does a "soft" switch, merging any local changes into the target |
| 141 | version, whereas [/help/checkout | checkout] does not |
| 142 | automatically sync and does a "hard" switch, overwriting local |
| 143 | changes if told to do so.</p> |
| 144 | |
| 145 | <h2 id="config">Configuring Your Local Repository</h2> |
| 146 | |
| 147 | <p>When you create a new repository, either by cloning an existing |
| 148 | project or create a new project of your own, you usually want to do some |
| 149 | local configuration. This is easily accomplished using the web-server |
| 150 | that is built into fossil. Start the fossil web server like this: |
| @@ -173,11 +172,11 @@ | |
| 172 | should, change this after you create a few users.</p> |
| 173 | |
| 174 | <p>When you are finished configuring, just press Control-C or use |
| 175 | the <b>kill</b> command to shut down the mini-server.</p> |
| 176 | |
| 177 | <h2 id="changes">Making Changes</h2> |
| 178 | |
| 179 | <p>To add new files to your project, or remove old files, use these |
| 180 | commands:</p> |
| 181 | |
| 182 | <blockquote> |
| @@ -201,11 +200,11 @@ | |
| 200 | feature can be disabled. (More information about |
| 201 | [./concepts.wiki#workflow|autosync] and how to disable it.) |
| 202 | Remember that your coworkers can not see your changes until you |
| 203 | commit and push them.</p> |
| 204 | |
| 205 | <h2 id="sharing">Sharing Changes</h2> |
| 206 | |
| 207 | <p>When [./concepts.wiki#workflow|autosync] is turned off, |
| 208 | the changes you [/help/commit | commit] are only |
| 209 | on your local repository. |
| 210 | To share those changes with other repositories, do:</p> |
| @@ -257,11 +256,11 @@ | |
| 256 | <p>Is similar to update except that it does not honor the autosync |
| 257 | setting, nor does it merge in local changes - it prefers to overwrite |
| 258 | them and fails if local changes exist unless the <tt>--force</tt> |
| 259 | flag is used.</p> |
| 260 | |
| 261 | <h2 id="branch" name="merge">Branching And Merging</h2> |
| 262 | |
| 263 | <p>Use the --branch option to the [/help/commit | commit] command |
| 264 | to start a new branch. Note that in Fossil, branches are normally |
| 265 | created when you commit, not before you start editing. You can |
| 266 | use the [/help/branch | branch new] command to create a new branch |
| @@ -315,11 +314,11 @@ | |
| 314 | mistake. Undo and redo only work for changes that have |
| 315 | not yet been checked in using commit and there is only a single |
| 316 | level of undo/redo.</p> |
| 317 | |
| 318 | |
| 319 | <h2 id="server">Setting Up A Server</h2> |
| 320 | |
| 321 | <p>Fossil can act as a stand-alone web server using one of these |
| 322 | commands:</p> |
| 323 | |
| 324 | <blockquote> |
| @@ -347,12 +346,11 @@ | |
| 346 | </ul> |
| 347 | |
| 348 | <p>The [./selfhost.wiki | self-hosting fossil repositories] use |
| 349 | CGI. |
| 350 | |
| 351 | <h2 id="proxy">HTTP Proxies</h2> |
| 352 | |
| 353 | <p>If you are behind a restrictive firewall that requires you to use |
| 354 | an HTTP proxy to reach the internet, then you can configure the proxy |
| 355 | in three different ways. You can tell fossil about your proxy using |
| 356 | a command-line option on commands that use the network, |
| 357 |