Fossil SCM
Fixed typos in commit [aa2fdc286c].
Commit
8cf380a48ef986e3e9ebea228ec755956315c53d
Parent
aa2fdc286c5e673…
1 file changed
+5
-5
+5
-5
| --- www/sync.wiki | ||
| +++ www/sync.wiki | ||
| @@ -234,11 +234,11 @@ | ||
| 234 | 234 | <b>clone</b> <i>protocol-version sequence-number</i> |
| 235 | 235 | </blockquote> |
| 236 | 236 | |
| 237 | 237 | <h4>3.5.1 Protocol 2</h4> |
| 238 | 238 | |
| 239 | -<p>The latest clients since a two-argument clone message with a | |
| 239 | +<p>The latest clients send a two-argument clone message with a | |
| 240 | 240 | protocol version of "2". (Future versions of Fossil might use larger |
| 241 | 241 | protocol version numbers.) The sequence-number sent is the number |
| 242 | 242 | of artifacts received so far. For the first clone message, the |
| 243 | 243 | sequence number if 0. The server will respond by sending file |
| 244 | 244 | cards for some number of artifacts up to the maximum message size. |
| @@ -264,11 +264,11 @@ | ||
| 264 | 264 | to a blank clone card by sending an "igot" card for every artifact in the |
| 265 | 265 | repository. The client will then issue "gimme" cards to pull down all the |
| 266 | 266 | content it needs. |
| 267 | 267 | |
| 268 | 268 | <p>The legacy protocol works well for smaller repositories (50MB with 50,000 |
| 269 | -artifacts) but because too slow and unwieldy for larger repositories. | |
| 269 | +artifacts) but is too slow and unwieldy for larger repositories. | |
| 270 | 270 | The version 2 protocol is an effort to improve performance. Further |
| 271 | 271 | performance improvements with higher-numbered clone protocols are |
| 272 | 272 | possible in future versions of Fossil. |
| 273 | 273 | |
| 274 | 274 | <h3>3.6 Igot Cards</h3> |
| @@ -390,14 +390,14 @@ | ||
| 390 | 390 | "config" card. |
| 391 | 391 | |
| 392 | 392 | <p>If the configuration-name begins with "@", that refers to a class of |
| 393 | 393 | values instead of a single value. The content of these configuration items |
| 394 | 394 | is returned in a "config" card that contains pure SQL text that is |
| 395 | -intended to evaluated by the client. | |
| 395 | +intended to be evaluated by the client. | |
| 396 | 396 | |
| 397 | 397 | <p>The @user and @concealed configuration items contain sensitive information |
| 398 | -are ignored for clients without sufficient privilege. | |
| 398 | +and are ignored for clients without sufficient privilege. | |
| 399 | 399 | |
| 400 | 400 | <h3>3.10 Configuration Cards</h3> |
| 401 | 401 | |
| 402 | 402 | <p>A "config" card is used to send configuration information from client |
| 403 | 403 | to server (in response to a "fossil configuration push" command) or |
| @@ -408,11 +408,11 @@ | ||
| 408 | 408 | <b>config</b> <i>configuration-name size</i> <b>\n</b> <i>content</i> |
| 409 | 409 | </blockquote> |
| 410 | 410 | |
| 411 | 411 | <p>The server will only accept a config card if the user has |
| 412 | 412 | "Admin" privilege. A client will only accept a config card if |
| 413 | -it had sent a correponding reqconfig card in its request. | |
| 413 | +it had sent a corresponding reqconfig card in its request. | |
| 414 | 414 | |
| 415 | 415 | <p>The content of the configuration item is used to overwrite the |
| 416 | 416 | corresponding configuration data in the receiver. |
| 417 | 417 | |
| 418 | 418 | <h3>3.11 Error Cards</h3> |
| 419 | 419 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -234,11 +234,11 @@ | |
| 234 | <b>clone</b> <i>protocol-version sequence-number</i> |
| 235 | </blockquote> |
| 236 | |
| 237 | <h4>3.5.1 Protocol 2</h4> |
| 238 | |
| 239 | <p>The latest clients since a two-argument clone message with a |
| 240 | protocol version of "2". (Future versions of Fossil might use larger |
| 241 | protocol version numbers.) The sequence-number sent is the number |
| 242 | of artifacts received so far. For the first clone message, the |
| 243 | sequence number if 0. The server will respond by sending file |
| 244 | cards for some number of artifacts up to the maximum message size. |
| @@ -264,11 +264,11 @@ | |
| 264 | to a blank clone card by sending an "igot" card for every artifact in the |
| 265 | repository. The client will then issue "gimme" cards to pull down all the |
| 266 | content it needs. |
| 267 | |
| 268 | <p>The legacy protocol works well for smaller repositories (50MB with 50,000 |
| 269 | artifacts) but because too slow and unwieldy for larger repositories. |
| 270 | The version 2 protocol is an effort to improve performance. Further |
| 271 | performance improvements with higher-numbered clone protocols are |
| 272 | possible in future versions of Fossil. |
| 273 | |
| 274 | <h3>3.6 Igot Cards</h3> |
| @@ -390,14 +390,14 @@ | |
| 390 | "config" card. |
| 391 | |
| 392 | <p>If the configuration-name begins with "@", that refers to a class of |
| 393 | values instead of a single value. The content of these configuration items |
| 394 | is returned in a "config" card that contains pure SQL text that is |
| 395 | intended to evaluated by the client. |
| 396 | |
| 397 | <p>The @user and @concealed configuration items contain sensitive information |
| 398 | are ignored for clients without sufficient privilege. |
| 399 | |
| 400 | <h3>3.10 Configuration Cards</h3> |
| 401 | |
| 402 | <p>A "config" card is used to send configuration information from client |
| 403 | to server (in response to a "fossil configuration push" command) or |
| @@ -408,11 +408,11 @@ | |
| 408 | <b>config</b> <i>configuration-name size</i> <b>\n</b> <i>content</i> |
| 409 | </blockquote> |
| 410 | |
| 411 | <p>The server will only accept a config card if the user has |
| 412 | "Admin" privilege. A client will only accept a config card if |
| 413 | it had sent a correponding reqconfig card in its request. |
| 414 | |
| 415 | <p>The content of the configuration item is used to overwrite the |
| 416 | corresponding configuration data in the receiver. |
| 417 | |
| 418 | <h3>3.11 Error Cards</h3> |
| 419 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -234,11 +234,11 @@ | |
| 234 | <b>clone</b> <i>protocol-version sequence-number</i> |
| 235 | </blockquote> |
| 236 | |
| 237 | <h4>3.5.1 Protocol 2</h4> |
| 238 | |
| 239 | <p>The latest clients send a two-argument clone message with a |
| 240 | protocol version of "2". (Future versions of Fossil might use larger |
| 241 | protocol version numbers.) The sequence-number sent is the number |
| 242 | of artifacts received so far. For the first clone message, the |
| 243 | sequence number if 0. The server will respond by sending file |
| 244 | cards for some number of artifacts up to the maximum message size. |
| @@ -264,11 +264,11 @@ | |
| 264 | to a blank clone card by sending an "igot" card for every artifact in the |
| 265 | repository. The client will then issue "gimme" cards to pull down all the |
| 266 | content it needs. |
| 267 | |
| 268 | <p>The legacy protocol works well for smaller repositories (50MB with 50,000 |
| 269 | artifacts) but is too slow and unwieldy for larger repositories. |
| 270 | The version 2 protocol is an effort to improve performance. Further |
| 271 | performance improvements with higher-numbered clone protocols are |
| 272 | possible in future versions of Fossil. |
| 273 | |
| 274 | <h3>3.6 Igot Cards</h3> |
| @@ -390,14 +390,14 @@ | |
| 390 | "config" card. |
| 391 | |
| 392 | <p>If the configuration-name begins with "@", that refers to a class of |
| 393 | values instead of a single value. The content of these configuration items |
| 394 | is returned in a "config" card that contains pure SQL text that is |
| 395 | intended to be evaluated by the client. |
| 396 | |
| 397 | <p>The @user and @concealed configuration items contain sensitive information |
| 398 | and are ignored for clients without sufficient privilege. |
| 399 | |
| 400 | <h3>3.10 Configuration Cards</h3> |
| 401 | |
| 402 | <p>A "config" card is used to send configuration information from client |
| 403 | to server (in response to a "fossil configuration push" command) or |
| @@ -408,11 +408,11 @@ | |
| 408 | <b>config</b> <i>configuration-name size</i> <b>\n</b> <i>content</i> |
| 409 | </blockquote> |
| 410 | |
| 411 | <p>The server will only accept a config card if the user has |
| 412 | "Admin" privilege. A client will only accept a config card if |
| 413 | it had sent a corresponding reqconfig card in its request. |
| 414 | |
| 415 | <p>The content of the configuration item is used to overwrite the |
| 416 | corresponding configuration data in the receiver. |
| 417 | |
| 418 | <h3>3.11 Error Cards</h3> |
| 419 |