Fossil SCM
Fix a documentation typo. Ticket [64386b2221309d].
Commit
11b3f31de959dc5bb81c8d20a4716d6354d2801a
Parent
c193d2c2e0fe513…
1 file changed
+1
-1
+1
-1
| --- www/branching.wiki | ||
| +++ www/branching.wiki | ||
| @@ -194,11 +194,11 @@ | ||
| 194 | 194 | are symbolic name tags. When a symbolic name tag is attached to a |
| 195 | 195 | check-in, that allows you to refer to that check-in by its symbolic |
| 196 | 196 | name rather than by its 40-character SHA1 hash name. When a symbolic name |
| 197 | 197 | tag propagates (as does the <b>sym-trunk</b> tag) then referring to that |
| 198 | 198 | name is the same as referring to the most recent check-in with that name. |
| 199 | -Thus the two tags on check-in once cause all decendents to be in the | |
| 199 | +Thus the two tags on check-in one cause all decendents to be in the | |
| 200 | 200 | "trunk" branch and to have the symbolic name "trunk". |
| 201 | 201 | |
| 202 | 202 | Check-in 4 has a <b>branch</b> tag which changes the name of the branch |
| 203 | 203 | to "test". The branch tag on check-in 4 propagates to check-ins 6 and 9. |
| 204 | 204 | But because tag propagation does not follow merge links, the <b>branch=test</b> |
| 205 | 205 |
| --- www/branching.wiki | |
| +++ www/branching.wiki | |
| @@ -194,11 +194,11 @@ | |
| 194 | are symbolic name tags. When a symbolic name tag is attached to a |
| 195 | check-in, that allows you to refer to that check-in by its symbolic |
| 196 | name rather than by its 40-character SHA1 hash name. When a symbolic name |
| 197 | tag propagates (as does the <b>sym-trunk</b> tag) then referring to that |
| 198 | name is the same as referring to the most recent check-in with that name. |
| 199 | Thus the two tags on check-in once cause all decendents to be in the |
| 200 | "trunk" branch and to have the symbolic name "trunk". |
| 201 | |
| 202 | Check-in 4 has a <b>branch</b> tag which changes the name of the branch |
| 203 | to "test". The branch tag on check-in 4 propagates to check-ins 6 and 9. |
| 204 | But because tag propagation does not follow merge links, the <b>branch=test</b> |
| 205 |
| --- www/branching.wiki | |
| +++ www/branching.wiki | |
| @@ -194,11 +194,11 @@ | |
| 194 | are symbolic name tags. When a symbolic name tag is attached to a |
| 195 | check-in, that allows you to refer to that check-in by its symbolic |
| 196 | name rather than by its 40-character SHA1 hash name. When a symbolic name |
| 197 | tag propagates (as does the <b>sym-trunk</b> tag) then referring to that |
| 198 | name is the same as referring to the most recent check-in with that name. |
| 199 | Thus the two tags on check-in one cause all decendents to be in the |
| 200 | "trunk" branch and to have the symbolic name "trunk". |
| 201 | |
| 202 | Check-in 4 has a <b>branch</b> tag which changes the name of the branch |
| 203 | to "test". The branch tag on check-in 4 propagates to check-ins 6 and 9. |
| 204 | But because tag propagation does not follow merge links, the <b>branch=test</b> |
| 205 |