Fossil SCM
Typo fixes thanks to rosscanning, ref [http://www.mail-archive.com/[email protected]/msg25775.html]
Commit
f98852a0df35ef2a0c81b67e9d669e71a1461982ec56f25fe798a3fa5e7d2131
Parent
92ea61837e98761…
3 files changed
+1
-1
+1
-1
+1
-1
+1
-1
| --- src/stash.c | ||
| +++ src/stash.c | ||
| @@ -428,11 +428,11 @@ | ||
| 428 | 428 | ** individual files in each changeset if -v or --verbose is used. |
| 429 | 429 | ** |
| 430 | 430 | ** fossil stash show|cat ?STASHID? ?DIFF-OPTIONS? |
| 431 | 431 | ** fossil stash gshow|gcat ?STASHID? ?DIFF-OPTIONS? |
| 432 | 432 | ** |
| 433 | -** Show the contents of a stash as a diff against it's baseline. | |
| 433 | +** Show the contents of a stash as a diff against its baseline. | |
| 434 | 434 | ** With gshow and gcat, gdiff-command is used instead of internal |
| 435 | 435 | ** diff logic. |
| 436 | 436 | ** |
| 437 | 437 | ** fossil stash pop |
| 438 | 438 | ** fossil stash apply ?STASHID? |
| 439 | 439 |
| --- src/stash.c | |
| +++ src/stash.c | |
| @@ -428,11 +428,11 @@ | |
| 428 | ** individual files in each changeset if -v or --verbose is used. |
| 429 | ** |
| 430 | ** fossil stash show|cat ?STASHID? ?DIFF-OPTIONS? |
| 431 | ** fossil stash gshow|gcat ?STASHID? ?DIFF-OPTIONS? |
| 432 | ** |
| 433 | ** Show the contents of a stash as a diff against it's baseline. |
| 434 | ** With gshow and gcat, gdiff-command is used instead of internal |
| 435 | ** diff logic. |
| 436 | ** |
| 437 | ** fossil stash pop |
| 438 | ** fossil stash apply ?STASHID? |
| 439 |
| --- src/stash.c | |
| +++ src/stash.c | |
| @@ -428,11 +428,11 @@ | |
| 428 | ** individual files in each changeset if -v or --verbose is used. |
| 429 | ** |
| 430 | ** fossil stash show|cat ?STASHID? ?DIFF-OPTIONS? |
| 431 | ** fossil stash gshow|gcat ?STASHID? ?DIFF-OPTIONS? |
| 432 | ** |
| 433 | ** Show the contents of a stash as a diff against its baseline. |
| 434 | ** With gshow and gcat, gdiff-command is used instead of internal |
| 435 | ** diff logic. |
| 436 | ** |
| 437 | ** fossil stash pop |
| 438 | ** fossil stash apply ?STASHID? |
| 439 |
+1
-1
| --- www/private.wiki | ||
| +++ www/private.wiki | ||
| @@ -87,8 +87,8 @@ | ||
| 87 | 87 | |
| 88 | 88 | <h2>Additional Notes</h2> |
| 89 | 89 | |
| 90 | 90 | All of the features above apply to <u>all</u> private branches in a |
| 91 | 91 | single repository at once. There is no mechanism in Fossil (currently) |
| 92 | -that allows you to push, pull, clone, sync, or scrub and individual | |
| 92 | +that allows you to push, pull, clone, sync, or scrub an individual | |
| 93 | 93 | private branch within a repository that contains multiple private |
| 94 | 94 | branches. |
| 95 | 95 |
| --- www/private.wiki | |
| +++ www/private.wiki | |
| @@ -87,8 +87,8 @@ | |
| 87 | |
| 88 | <h2>Additional Notes</h2> |
| 89 | |
| 90 | All of the features above apply to <u>all</u> private branches in a |
| 91 | single repository at once. There is no mechanism in Fossil (currently) |
| 92 | that allows you to push, pull, clone, sync, or scrub and individual |
| 93 | private branch within a repository that contains multiple private |
| 94 | branches. |
| 95 |
| --- www/private.wiki | |
| +++ www/private.wiki | |
| @@ -87,8 +87,8 @@ | |
| 87 | |
| 88 | <h2>Additional Notes</h2> |
| 89 | |
| 90 | All of the features above apply to <u>all</u> private branches in a |
| 91 | single repository at once. There is no mechanism in Fossil (currently) |
| 92 | that allows you to push, pull, clone, sync, or scrub an individual |
| 93 | private branch within a repository that contains multiple private |
| 94 | branches. |
| 95 |
+1
-1
| --- www/tech_overview.wiki | ||
| +++ www/tech_overview.wiki | ||
| @@ -206,11 +206,11 @@ | ||
| 206 | 206 | The metadata is held in various SQL tables in the repository database. |
| 207 | 207 | The metadata is designed to facilitate queries for the various timelines and |
| 208 | 208 | reports that Fossil generates. |
| 209 | 209 | As the functionality of Fossil evolves, |
| 210 | 210 | the schema for the metadata can and does change. |
| 211 | -But schema changes do no invalidate the repository. Remember that the | |
| 211 | +But schema changes do not invalidate the repository. Remember that the | |
| 212 | 212 | metadata contains no new information - only information that has been |
| 213 | 213 | extracted from the canonical artifacts and saved in a more useful form. |
| 214 | 214 | Hence, when the metadata schema changes, the prior metadata can be discarded |
| 215 | 215 | and the entire metadata corpus can be recomputed from the canonical |
| 216 | 216 | artifacts. That is what the |
| 217 | 217 |
| --- www/tech_overview.wiki | |
| +++ www/tech_overview.wiki | |
| @@ -206,11 +206,11 @@ | |
| 206 | The metadata is held in various SQL tables in the repository database. |
| 207 | The metadata is designed to facilitate queries for the various timelines and |
| 208 | reports that Fossil generates. |
| 209 | As the functionality of Fossil evolves, |
| 210 | the schema for the metadata can and does change. |
| 211 | But schema changes do no invalidate the repository. Remember that the |
| 212 | metadata contains no new information - only information that has been |
| 213 | extracted from the canonical artifacts and saved in a more useful form. |
| 214 | Hence, when the metadata schema changes, the prior metadata can be discarded |
| 215 | and the entire metadata corpus can be recomputed from the canonical |
| 216 | artifacts. That is what the |
| 217 |
| --- www/tech_overview.wiki | |
| +++ www/tech_overview.wiki | |
| @@ -206,11 +206,11 @@ | |
| 206 | The metadata is held in various SQL tables in the repository database. |
| 207 | The metadata is designed to facilitate queries for the various timelines and |
| 208 | reports that Fossil generates. |
| 209 | As the functionality of Fossil evolves, |
| 210 | the schema for the metadata can and does change. |
| 211 | But schema changes do not invalidate the repository. Remember that the |
| 212 | metadata contains no new information - only information that has been |
| 213 | extracted from the canonical artifacts and saved in a more useful form. |
| 214 | Hence, when the metadata schema changes, the prior metadata can be discarded |
| 215 | and the entire metadata corpus can be recomputed from the canonical |
| 216 | artifacts. That is what the |
| 217 |