Fossil SCM
Typo fixes reported in [forum:10167c5f79|forum post 10167c5f79].
Commit
382a61e327d62afb9097760d10f0030b82157f1346edc42becf99b16a349a8a3
Parent
dbc9e48ebfb47b4…
2 files changed
+3
-3
+3
-3
+3
-3
| --- www/faq.tcl | ||
| +++ www/faq.tcl | ||
| @@ -72,11 +72,11 @@ | ||
| 72 | 72 | command, you can add a tag to that check-in using the |
| 73 | 73 | "--tag <i>TAGNAME</i>" command-line option. You can repeat the --tag |
| 74 | 74 | option to give a check-in multiple tags. Tags need not be unique. So, |
| 75 | 75 | for example, it is common to give every released version a "release" tag. |
| 76 | 76 | |
| 77 | - If you want add a tag to an existing check-in, you can use the | |
| 77 | + If you want to add a tag to an existing check-in, you can use the | |
| 78 | 78 | <b>[/help/tag|tag]</b> command. For example: |
| 79 | 79 | |
| 80 | 80 | <pre> |
| 81 | 81 | <b>fossil [/help/branch|tag] add</b> <i>TAGNAME</i> <i>CHECK-IN</i> |
| 82 | 82 | </pre> |
| @@ -84,11 +84,11 @@ | ||
| 84 | 84 | The CHECK-IN in the previous line can be any |
| 85 | 85 | [./checkin_names.wiki | valid check-in name format]. |
| 86 | 86 | |
| 87 | 87 | You can also add (and remove) tags from a check-in using the |
| 88 | 88 | [./webui.wiki | web interface]. First locate the check-in that you |
| 89 | - what to tag on the timeline, then click on the link to go the detailed | |
| 89 | + want to tag on the timeline, then click on the link to go the detailed | |
| 90 | 90 | information page for that check-in. Then find the "<b>edit</b>" |
| 91 | 91 | link (near the "Commands:" label) and click on that. There are |
| 92 | 92 | controls on the edit page that allow new tags to be added and existing |
| 93 | 93 | tags to be removed. |
| 94 | 94 | } |
| @@ -96,11 +96,11 @@ | ||
| 96 | 96 | faq { |
| 97 | 97 | How do I create a private branch that won't get pushed back to the |
| 98 | 98 | main repository. |
| 99 | 99 | } { |
| 100 | 100 | Use the <b>--private</b> command-line option on the |
| 101 | - <b>commit</b> command. The result will be a check-in which exists on | |
| 101 | + <b>commit</b> command. The result will be a check-in which exists in | |
| 102 | 102 | your local repository only and is never pushed to other repositories. |
| 103 | 103 | All descendants of a private check-in are also private. |
| 104 | 104 | |
| 105 | 105 | Unless you specify something different using the <b>--branch</b> and/or |
| 106 | 106 | <b>--bgcolor</b> options, the new private check-in will be put on a branch |
| 107 | 107 |
| --- www/faq.tcl | |
| +++ www/faq.tcl | |
| @@ -72,11 +72,11 @@ | |
| 72 | command, you can add a tag to that check-in using the |
| 73 | "--tag <i>TAGNAME</i>" command-line option. You can repeat the --tag |
| 74 | option to give a check-in multiple tags. Tags need not be unique. So, |
| 75 | for example, it is common to give every released version a "release" tag. |
| 76 | |
| 77 | If you want add a tag to an existing check-in, you can use the |
| 78 | <b>[/help/tag|tag]</b> command. For example: |
| 79 | |
| 80 | <pre> |
| 81 | <b>fossil [/help/branch|tag] add</b> <i>TAGNAME</i> <i>CHECK-IN</i> |
| 82 | </pre> |
| @@ -84,11 +84,11 @@ | |
| 84 | The CHECK-IN in the previous line can be any |
| 85 | [./checkin_names.wiki | valid check-in name format]. |
| 86 | |
| 87 | You can also add (and remove) tags from a check-in using the |
| 88 | [./webui.wiki | web interface]. First locate the check-in that you |
| 89 | what to tag on the timeline, then click on the link to go the detailed |
| 90 | information page for that check-in. Then find the "<b>edit</b>" |
| 91 | link (near the "Commands:" label) and click on that. There are |
| 92 | controls on the edit page that allow new tags to be added and existing |
| 93 | tags to be removed. |
| 94 | } |
| @@ -96,11 +96,11 @@ | |
| 96 | faq { |
| 97 | How do I create a private branch that won't get pushed back to the |
| 98 | main repository. |
| 99 | } { |
| 100 | Use the <b>--private</b> command-line option on the |
| 101 | <b>commit</b> command. The result will be a check-in which exists on |
| 102 | your local repository only and is never pushed to other repositories. |
| 103 | All descendants of a private check-in are also private. |
| 104 | |
| 105 | Unless you specify something different using the <b>--branch</b> and/or |
| 106 | <b>--bgcolor</b> options, the new private check-in will be put on a branch |
| 107 |
| --- www/faq.tcl | |
| +++ www/faq.tcl | |
| @@ -72,11 +72,11 @@ | |
| 72 | command, you can add a tag to that check-in using the |
| 73 | "--tag <i>TAGNAME</i>" command-line option. You can repeat the --tag |
| 74 | option to give a check-in multiple tags. Tags need not be unique. So, |
| 75 | for example, it is common to give every released version a "release" tag. |
| 76 | |
| 77 | If you want to add a tag to an existing check-in, you can use the |
| 78 | <b>[/help/tag|tag]</b> command. For example: |
| 79 | |
| 80 | <pre> |
| 81 | <b>fossil [/help/branch|tag] add</b> <i>TAGNAME</i> <i>CHECK-IN</i> |
| 82 | </pre> |
| @@ -84,11 +84,11 @@ | |
| 84 | The CHECK-IN in the previous line can be any |
| 85 | [./checkin_names.wiki | valid check-in name format]. |
| 86 | |
| 87 | You can also add (and remove) tags from a check-in using the |
| 88 | [./webui.wiki | web interface]. First locate the check-in that you |
| 89 | want to tag on the timeline, then click on the link to go the detailed |
| 90 | information page for that check-in. Then find the "<b>edit</b>" |
| 91 | link (near the "Commands:" label) and click on that. There are |
| 92 | controls on the edit page that allow new tags to be added and existing |
| 93 | tags to be removed. |
| 94 | } |
| @@ -96,11 +96,11 @@ | |
| 96 | faq { |
| 97 | How do I create a private branch that won't get pushed back to the |
| 98 | main repository. |
| 99 | } { |
| 100 | Use the <b>--private</b> command-line option on the |
| 101 | <b>commit</b> command. The result will be a check-in which exists in |
| 102 | your local repository only and is never pushed to other repositories. |
| 103 | All descendants of a private check-in are also private. |
| 104 | |
| 105 | Unless you specify something different using the <b>--branch</b> and/or |
| 106 | <b>--bgcolor</b> options, the new private check-in will be put on a branch |
| 107 |
+3
-3
| --- www/faq.wiki | ||
| +++ www/faq.wiki | ||
| @@ -70,11 +70,11 @@ | ||
| 70 | 70 | command, you can add a tag to that check-in using the |
| 71 | 71 | "--tag <i>TAGNAME</i>" command-line option. You can repeat the --tag |
| 72 | 72 | option to give a check-in multiple tags. Tags need not be unique. So, |
| 73 | 73 | for example, it is common to give every released version a "release" tag. |
| 74 | 74 | |
| 75 | -If you want add a tag to an existing check-in, you can use the | |
| 75 | +If you want to add a tag to an existing check-in, you can use the | |
| 76 | 76 | <b>[/help/tag|tag]</b> command. For example: |
| 77 | 77 | |
| 78 | 78 | <pre> |
| 79 | 79 | <b>fossil [/help/branch|tag] add</b> <i>TAGNAME</i> <i>CHECK-IN</i> |
| 80 | 80 | </pre> |
| @@ -82,21 +82,21 @@ | ||
| 82 | 82 | The CHECK-IN in the previous line can be any |
| 83 | 83 | [./checkin_names.wiki | valid check-in name format]. |
| 84 | 84 | |
| 85 | 85 | You can also add (and remove) tags from a check-in using the |
| 86 | 86 | [./webui.wiki | web interface]. First locate the check-in that you |
| 87 | -what to tag on the timeline, then click on the link to go the detailed | |
| 87 | +want to tag on the timeline, then click on the link to go the detailed | |
| 88 | 88 | information page for that check-in. Then find the "<b>edit</b>" |
| 89 | 89 | link (near the "Commands:" label) and click on that. There are |
| 90 | 90 | controls on the edit page that allow new tags to be added and existing |
| 91 | 91 | tags to be removed.</li> |
| 92 | 92 | |
| 93 | 93 | <p id="q5"><b>(5) How do I create a private branch that won't get pushed back to the |
| 94 | 94 | main repository.</b></p> |
| 95 | 95 | |
| 96 | 96 | Use the <b>--private</b> command-line option on the |
| 97 | -<b>commit</b> command. The result will be a check-in which exists on | |
| 97 | +<b>commit</b> command. The result will be a check-in which exists in | |
| 98 | 98 | your local repository only and is never pushed to other repositories. |
| 99 | 99 | All descendants of a private check-in are also private. |
| 100 | 100 | |
| 101 | 101 | Unless you specify something different using the <b>--branch</b> and/or |
| 102 | 102 | <b>--bgcolor</b> options, the new private check-in will be put on a branch |
| 103 | 103 |
| --- www/faq.wiki | |
| +++ www/faq.wiki | |
| @@ -70,11 +70,11 @@ | |
| 70 | command, you can add a tag to that check-in using the |
| 71 | "--tag <i>TAGNAME</i>" command-line option. You can repeat the --tag |
| 72 | option to give a check-in multiple tags. Tags need not be unique. So, |
| 73 | for example, it is common to give every released version a "release" tag. |
| 74 | |
| 75 | If you want add a tag to an existing check-in, you can use the |
| 76 | <b>[/help/tag|tag]</b> command. For example: |
| 77 | |
| 78 | <pre> |
| 79 | <b>fossil [/help/branch|tag] add</b> <i>TAGNAME</i> <i>CHECK-IN</i> |
| 80 | </pre> |
| @@ -82,21 +82,21 @@ | |
| 82 | The CHECK-IN in the previous line can be any |
| 83 | [./checkin_names.wiki | valid check-in name format]. |
| 84 | |
| 85 | You can also add (and remove) tags from a check-in using the |
| 86 | [./webui.wiki | web interface]. First locate the check-in that you |
| 87 | what to tag on the timeline, then click on the link to go the detailed |
| 88 | information page for that check-in. Then find the "<b>edit</b>" |
| 89 | link (near the "Commands:" label) and click on that. There are |
| 90 | controls on the edit page that allow new tags to be added and existing |
| 91 | tags to be removed.</li> |
| 92 | |
| 93 | <p id="q5"><b>(5) How do I create a private branch that won't get pushed back to the |
| 94 | main repository.</b></p> |
| 95 | |
| 96 | Use the <b>--private</b> command-line option on the |
| 97 | <b>commit</b> command. The result will be a check-in which exists on |
| 98 | your local repository only and is never pushed to other repositories. |
| 99 | All descendants of a private check-in are also private. |
| 100 | |
| 101 | Unless you specify something different using the <b>--branch</b> and/or |
| 102 | <b>--bgcolor</b> options, the new private check-in will be put on a branch |
| 103 |
| --- www/faq.wiki | |
| +++ www/faq.wiki | |
| @@ -70,11 +70,11 @@ | |
| 70 | command, you can add a tag to that check-in using the |
| 71 | "--tag <i>TAGNAME</i>" command-line option. You can repeat the --tag |
| 72 | option to give a check-in multiple tags. Tags need not be unique. So, |
| 73 | for example, it is common to give every released version a "release" tag. |
| 74 | |
| 75 | If you want to add a tag to an existing check-in, you can use the |
| 76 | <b>[/help/tag|tag]</b> command. For example: |
| 77 | |
| 78 | <pre> |
| 79 | <b>fossil [/help/branch|tag] add</b> <i>TAGNAME</i> <i>CHECK-IN</i> |
| 80 | </pre> |
| @@ -82,21 +82,21 @@ | |
| 82 | The CHECK-IN in the previous line can be any |
| 83 | [./checkin_names.wiki | valid check-in name format]. |
| 84 | |
| 85 | You can also add (and remove) tags from a check-in using the |
| 86 | [./webui.wiki | web interface]. First locate the check-in that you |
| 87 | want to tag on the timeline, then click on the link to go the detailed |
| 88 | information page for that check-in. Then find the "<b>edit</b>" |
| 89 | link (near the "Commands:" label) and click on that. There are |
| 90 | controls on the edit page that allow new tags to be added and existing |
| 91 | tags to be removed.</li> |
| 92 | |
| 93 | <p id="q5"><b>(5) How do I create a private branch that won't get pushed back to the |
| 94 | main repository.</b></p> |
| 95 | |
| 96 | Use the <b>--private</b> command-line option on the |
| 97 | <b>commit</b> command. The result will be a check-in which exists in |
| 98 | your local repository only and is never pushed to other repositories. |
| 99 | All descendants of a private check-in are also private. |
| 100 | |
| 101 | Unless you specify something different using the <b>--branch</b> and/or |
| 102 | <b>--bgcolor</b> options, the new private check-in will be put on a branch |
| 103 |