Fossil SCM
Hopefully the last of the changes for www/sync.wiki
Commit
1db8e43e12923b02c75a5e1c518695ef74ec84c725f881dcf93fa0b83aeda46f
Parent
d25826d447c7fd5…
1 file changed
+2
-2
+2
-2
| --- www/sync.wiki | ||
| +++ www/sync.wiki | ||
| @@ -881,11 +881,11 @@ | ||
| 881 | 881 | <h2 id="strategies">5.0 Synchronization Strategies</h2> |
| 882 | 882 | |
| 883 | 883 | <h3 id="pull-strategy">5.1 Pull</h3> |
| 884 | 884 | |
| 885 | 885 | A typical pull operation proceeds as shown below. Details |
| 886 | -of the actual implementation may very slightly but the gist of | |
| 886 | +of the actual implementation may vary slightly but the gist of | |
| 887 | 887 | a pull is captured in the following steps: |
| 888 | 888 | |
| 889 | 889 | <ol> |
| 890 | 890 | <li>The client sends login and pull cards. |
| 891 | 891 | <li>The client sends a cookie card if it has previously received a cookie. |
| @@ -1091,6 +1091,6 @@ | ||
| 1091 | 1091 | </ol> |
| 1092 | 1092 | |
| 1093 | 1093 | In a complex debugging situation, you can run the command |
| 1094 | 1094 | "fossil sync --transport-command ./debugging_script" where |
| 1095 | 1095 | "debugging_script" is some script of your own that invokes |
| 1096 | -the anomolous behavior your are trying to debug. | |
| 1096 | +the anomalous behavior you are trying to debug. | |
| 1097 | 1097 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -881,11 +881,11 @@ | |
| 881 | <h2 id="strategies">5.0 Synchronization Strategies</h2> |
| 882 | |
| 883 | <h3 id="pull-strategy">5.1 Pull</h3> |
| 884 | |
| 885 | A typical pull operation proceeds as shown below. Details |
| 886 | of the actual implementation may very slightly but the gist of |
| 887 | a pull is captured in the following steps: |
| 888 | |
| 889 | <ol> |
| 890 | <li>The client sends login and pull cards. |
| 891 | <li>The client sends a cookie card if it has previously received a cookie. |
| @@ -1091,6 +1091,6 @@ | |
| 1091 | </ol> |
| 1092 | |
| 1093 | In a complex debugging situation, you can run the command |
| 1094 | "fossil sync --transport-command ./debugging_script" where |
| 1095 | "debugging_script" is some script of your own that invokes |
| 1096 | the anomolous behavior your are trying to debug. |
| 1097 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -881,11 +881,11 @@ | |
| 881 | <h2 id="strategies">5.0 Synchronization Strategies</h2> |
| 882 | |
| 883 | <h3 id="pull-strategy">5.1 Pull</h3> |
| 884 | |
| 885 | A typical pull operation proceeds as shown below. Details |
| 886 | of the actual implementation may vary slightly but the gist of |
| 887 | a pull is captured in the following steps: |
| 888 | |
| 889 | <ol> |
| 890 | <li>The client sends login and pull cards. |
| 891 | <li>The client sends a cookie card if it has previously received a cookie. |
| @@ -1091,6 +1091,6 @@ | |
| 1091 | </ol> |
| 1092 | |
| 1093 | In a complex debugging situation, you can run the command |
| 1094 | "fossil sync --transport-command ./debugging_script" where |
| 1095 | "debugging_script" is some script of your own that invokes |
| 1096 | the anomalous behavior you are trying to debug. |
| 1097 |