Fossil SCM
Fix broken hyperlinks on the tech_overview.wiki page.
Commit
3018d519c8d61073720e2e84b852af64a621e1b914179450b71faf9ede338979
Parent
c7e55d9cacd4c7c…
1 file changed
+5
-5
+5
-5
| --- www/tech_overview.wiki | ||
| +++ www/tech_overview.wiki | ||
| @@ -53,11 +53,11 @@ | ||
| 53 | 53 | checkout for a project and contains state information that is unique |
| 54 | 54 | to that working checkout. |
| 55 | 55 | |
| 56 | 56 | Fossil does not always use all three database files. The web interface, |
| 57 | 57 | for example, typically only uses the repository database. And the |
| 58 | -[/help/all | fossil setting] command only opens the configuration database | |
| 58 | +[/help/all | fossil settings] command only opens the configuration database | |
| 59 | 59 | when the --global option is used. But other commands use all three |
| 60 | 60 | databases at once. For example, the [/help/status | fossil status] |
| 61 | 61 | command will first locate the checkout database, then use the checkout |
| 62 | 62 | database to find the repository database, then open the configuration |
| 63 | 63 | database. Whenever multiple databases are used at the same time, |
| @@ -70,20 +70,20 @@ | ||
| 70 | 70 | <table border="1" width="80%" cellpadding="0" align="center"> |
| 71 | 71 | <tr> |
| 72 | 72 | <td width="33%" valign="top"> |
| 73 | 73 | <h3 align="center">Configuration Database<br>"~/.fossil"</h3> |
| 74 | 74 | <ul> |
| 75 | -<li>Global [/help/setting |settings] | |
| 75 | +<li>Global [/help/settings |settings] | |
| 76 | 76 | <li>List of active repositories used by the [/help/all | all] command |
| 77 | 77 | </ul> |
| 78 | 78 | </td> |
| 79 | 79 | <td width="34%" valign="top"> |
| 80 | 80 | <h3 align="center">Repository Database<br>"<i>project</i>.fossil"</h3> |
| 81 | 81 | <ul> |
| 82 | 82 | <li>[./fileformat.wiki | Global state of the project] |
| 83 | 83 | encoded using delta-compression |
| 84 | -<li>Local [/help/setting|settings] | |
| 84 | +<li>Local [/help/settings|settings] | |
| 85 | 85 | <li>Web interface display preferences |
| 86 | 86 | <li>User credentials and permissions |
| 87 | 87 | <li>Metadata about the global state to facilitate rapid |
| 88 | 88 | queries |
| 89 | 89 | </ul> |
| @@ -110,11 +110,11 @@ | ||
| 110 | 110 | <h3>2.1 The Configuration Database</h3> |
| 111 | 111 | |
| 112 | 112 | The configuration database holds cross-repository preferences and a list of all |
| 113 | 113 | repositories for a single user. |
| 114 | 114 | |
| 115 | -The [/help/setting | fossil setting] command can be used to specify various | |
| 115 | +The [/help/settings | fossil settings] command can be used to specify various | |
| 116 | 116 | operating parameters and preferences for Fossil repositories. Settings can |
| 117 | 117 | apply to a single repository, or they can apply globally to all repositories |
| 118 | 118 | for a user. If both a global and a repository value exists for a setting, |
| 119 | 119 | then the repository-specific value takes precedence. All of the settings |
| 120 | 120 | have reasonable defaults, and so many users will never need to change them. |
| @@ -237,11 +237,11 @@ | ||
| 237 | 237 | * The project logo image |
| 238 | 238 | * Fields of tickets that are considered "significant" and which are |
| 239 | 239 | therefore collected from artifacts and made available for display |
| 240 | 240 | * Templates for screens to view, edit, and create tickets |
| 241 | 241 | * Ticket report formats and display preferences |
| 242 | - * Local values for [/help/setting | settings] that override the | |
| 242 | + * Local values for [/help/settings | settings] that override the | |
| 243 | 243 | global values defined in the per-user configuration database. |
| 244 | 244 | |
| 245 | 245 | Though the display and processing preferences do not move between |
| 246 | 246 | repository instances using [/help/sync | fossil sync], this information |
| 247 | 247 | can be shared between repositories using the |
| 248 | 248 |
| --- www/tech_overview.wiki | |
| +++ www/tech_overview.wiki | |
| @@ -53,11 +53,11 @@ | |
| 53 | checkout for a project and contains state information that is unique |
| 54 | to that working checkout. |
| 55 | |
| 56 | Fossil does not always use all three database files. The web interface, |
| 57 | for example, typically only uses the repository database. And the |
| 58 | [/help/all | fossil setting] command only opens the configuration database |
| 59 | when the --global option is used. But other commands use all three |
| 60 | databases at once. For example, the [/help/status | fossil status] |
| 61 | command will first locate the checkout database, then use the checkout |
| 62 | database to find the repository database, then open the configuration |
| 63 | database. Whenever multiple databases are used at the same time, |
| @@ -70,20 +70,20 @@ | |
| 70 | <table border="1" width="80%" cellpadding="0" align="center"> |
| 71 | <tr> |
| 72 | <td width="33%" valign="top"> |
| 73 | <h3 align="center">Configuration Database<br>"~/.fossil"</h3> |
| 74 | <ul> |
| 75 | <li>Global [/help/setting |settings] |
| 76 | <li>List of active repositories used by the [/help/all | all] command |
| 77 | </ul> |
| 78 | </td> |
| 79 | <td width="34%" valign="top"> |
| 80 | <h3 align="center">Repository Database<br>"<i>project</i>.fossil"</h3> |
| 81 | <ul> |
| 82 | <li>[./fileformat.wiki | Global state of the project] |
| 83 | encoded using delta-compression |
| 84 | <li>Local [/help/setting|settings] |
| 85 | <li>Web interface display preferences |
| 86 | <li>User credentials and permissions |
| 87 | <li>Metadata about the global state to facilitate rapid |
| 88 | queries |
| 89 | </ul> |
| @@ -110,11 +110,11 @@ | |
| 110 | <h3>2.1 The Configuration Database</h3> |
| 111 | |
| 112 | The configuration database holds cross-repository preferences and a list of all |
| 113 | repositories for a single user. |
| 114 | |
| 115 | The [/help/setting | fossil setting] command can be used to specify various |
| 116 | operating parameters and preferences for Fossil repositories. Settings can |
| 117 | apply to a single repository, or they can apply globally to all repositories |
| 118 | for a user. If both a global and a repository value exists for a setting, |
| 119 | then the repository-specific value takes precedence. All of the settings |
| 120 | have reasonable defaults, and so many users will never need to change them. |
| @@ -237,11 +237,11 @@ | |
| 237 | * The project logo image |
| 238 | * Fields of tickets that are considered "significant" and which are |
| 239 | therefore collected from artifacts and made available for display |
| 240 | * Templates for screens to view, edit, and create tickets |
| 241 | * Ticket report formats and display preferences |
| 242 | * Local values for [/help/setting | settings] that override the |
| 243 | global values defined in the per-user configuration database. |
| 244 | |
| 245 | Though the display and processing preferences do not move between |
| 246 | repository instances using [/help/sync | fossil sync], this information |
| 247 | can be shared between repositories using the |
| 248 |
| --- www/tech_overview.wiki | |
| +++ www/tech_overview.wiki | |
| @@ -53,11 +53,11 @@ | |
| 53 | checkout for a project and contains state information that is unique |
| 54 | to that working checkout. |
| 55 | |
| 56 | Fossil does not always use all three database files. The web interface, |
| 57 | for example, typically only uses the repository database. And the |
| 58 | [/help/all | fossil settings] command only opens the configuration database |
| 59 | when the --global option is used. But other commands use all three |
| 60 | databases at once. For example, the [/help/status | fossil status] |
| 61 | command will first locate the checkout database, then use the checkout |
| 62 | database to find the repository database, then open the configuration |
| 63 | database. Whenever multiple databases are used at the same time, |
| @@ -70,20 +70,20 @@ | |
| 70 | <table border="1" width="80%" cellpadding="0" align="center"> |
| 71 | <tr> |
| 72 | <td width="33%" valign="top"> |
| 73 | <h3 align="center">Configuration Database<br>"~/.fossil"</h3> |
| 74 | <ul> |
| 75 | <li>Global [/help/settings |settings] |
| 76 | <li>List of active repositories used by the [/help/all | all] command |
| 77 | </ul> |
| 78 | </td> |
| 79 | <td width="34%" valign="top"> |
| 80 | <h3 align="center">Repository Database<br>"<i>project</i>.fossil"</h3> |
| 81 | <ul> |
| 82 | <li>[./fileformat.wiki | Global state of the project] |
| 83 | encoded using delta-compression |
| 84 | <li>Local [/help/settings|settings] |
| 85 | <li>Web interface display preferences |
| 86 | <li>User credentials and permissions |
| 87 | <li>Metadata about the global state to facilitate rapid |
| 88 | queries |
| 89 | </ul> |
| @@ -110,11 +110,11 @@ | |
| 110 | <h3>2.1 The Configuration Database</h3> |
| 111 | |
| 112 | The configuration database holds cross-repository preferences and a list of all |
| 113 | repositories for a single user. |
| 114 | |
| 115 | The [/help/settings | fossil settings] command can be used to specify various |
| 116 | operating parameters and preferences for Fossil repositories. Settings can |
| 117 | apply to a single repository, or they can apply globally to all repositories |
| 118 | for a user. If both a global and a repository value exists for a setting, |
| 119 | then the repository-specific value takes precedence. All of the settings |
| 120 | have reasonable defaults, and so many users will never need to change them. |
| @@ -237,11 +237,11 @@ | |
| 237 | * The project logo image |
| 238 | * Fields of tickets that are considered "significant" and which are |
| 239 | therefore collected from artifacts and made available for display |
| 240 | * Templates for screens to view, edit, and create tickets |
| 241 | * Ticket report formats and display preferences |
| 242 | * Local values for [/help/settings | settings] that override the |
| 243 | global values defined in the per-user configuration database. |
| 244 | |
| 245 | Though the display and processing preferences do not move between |
| 246 | repository instances using [/help/sync | fossil sync], this information |
| 247 | can be shared between repositories using the |
| 248 |