Fossil SCM
Explain how Fossil ignores success/failure of a mirror run and only triggers the next run based on a repo change or --force.
Commit
ff63c1eead2393c353b034ec6079236603f1de3a92e8ae3e567253ba880cee7f
Parent
97959c893622b94…
1 file changed
+7
| --- www/mirrortogithub.md | ||
| +++ www/mirrortogithub.md | ||
| @@ -77,10 +77,17 @@ | ||
| 77 | 77 | <pre>$ fossil git status</pre> |
| 78 | 78 | </blockquote> |
| 79 | 79 | </ol> |
| 80 | 80 | |
| 81 | 81 | ## Notes: |
| 82 | + | |
| 83 | + * Unless you specify --force, the mirroring only happens if the Fossil | |
| 84 | + repo has changed, with Fossil reporting "no changes", because Fossil | |
| 85 | + does not care about the success or failure of the mirror run. If a mirror | |
| 86 | + run failed (for example, due to an incorrect password, or a transient | |
| 87 | + error at github.com), Fossil will not retry until there has been a repo | |
| 88 | + change or --force is supplied. | |
| 82 | 89 | |
| 83 | 90 | * The mirroring is one-way. If you check in changes on GitHub, those |
| 84 | 91 | changes will not be reabsorbed by Fossil. There are technical problems |
| 85 | 92 | that make a two-way mirror all but impossible. (This is not to be |
| 86 | 93 | confused with the ability to import a Fossil mirror from Github back |
| 87 | 94 |
| --- www/mirrortogithub.md | |
| +++ www/mirrortogithub.md | |
| @@ -77,10 +77,17 @@ | |
| 77 | <pre>$ fossil git status</pre> |
| 78 | </blockquote> |
| 79 | </ol> |
| 80 | |
| 81 | ## Notes: |
| 82 | |
| 83 | * The mirroring is one-way. If you check in changes on GitHub, those |
| 84 | changes will not be reabsorbed by Fossil. There are technical problems |
| 85 | that make a two-way mirror all but impossible. (This is not to be |
| 86 | confused with the ability to import a Fossil mirror from Github back |
| 87 |
| --- www/mirrortogithub.md | |
| +++ www/mirrortogithub.md | |
| @@ -77,10 +77,17 @@ | |
| 77 | <pre>$ fossil git status</pre> |
| 78 | </blockquote> |
| 79 | </ol> |
| 80 | |
| 81 | ## Notes: |
| 82 | |
| 83 | * Unless you specify --force, the mirroring only happens if the Fossil |
| 84 | repo has changed, with Fossil reporting "no changes", because Fossil |
| 85 | does not care about the success or failure of the mirror run. If a mirror |
| 86 | run failed (for example, due to an incorrect password, or a transient |
| 87 | error at github.com), Fossil will not retry until there has been a repo |
| 88 | change or --force is supplied. |
| 89 | |
| 90 | * The mirroring is one-way. If you check in changes on GitHub, those |
| 91 | changes will not be reabsorbed by Fossil. There are technical problems |
| 92 | that make a two-way mirror all but impossible. (This is not to be |
| 93 | confused with the ability to import a Fossil mirror from Github back |
| 94 |