Fossil SCM
Minor corrections to documentation.
Commit
f1b148df7fd0e5819df6704560aea720fa6ec128
Parent
3fa7965c640d63c…
3 files changed
+3
-3
+1
-1
+3
-3
+3
-3
| --- www/fileformat.wiki | ||
| +++ www/fileformat.wiki | ||
| @@ -28,12 +28,12 @@ | ||
| 28 | 28 | The local state is not composed of artifacts and is not intended to be enduring. |
| 29 | 29 | This document is concerned with global state only. Local state is only |
| 30 | 30 | mentioned here in order to distinguish it from global state. |
| 31 | 31 | |
| 32 | 32 | Each artifact in the repository is named by its SHA1 hash. |
| 33 | -No prefixes or meta information is added to a artifact before | |
| 34 | -its hash is computed. The name of a artifact in the repository | |
| 33 | +No prefixes or meta information is added to an artifact before | |
| 34 | +its hash is computed. The name of an artifact in the repository | |
| 35 | 35 | is exactly the same SHA1 hash that is computed by sha1sum |
| 36 | 36 | on the file as it exists in your source tree.</p> |
| 37 | 37 | |
| 38 | 38 | Some artifacts have a particular format which gives them special |
| 39 | 39 | meaning to fossil. Fossil recognizes: |
| @@ -238,11 +238,11 @@ | ||
| 238 | 238 | [/artifact/28987096ac | here]. |
| 239 | 239 | |
| 240 | 240 | <a name="cluster"></a> |
| 241 | 241 | <h2>2.0 Clusters</h2> |
| 242 | 242 | |
| 243 | -A cluster is a artifact that declares the existence of other artifacts. | |
| 243 | +A cluster is an artifact that declares the existence of other artifacts. | |
| 244 | 244 | Clusters are used during repository synchronization to help |
| 245 | 245 | reduce network traffic. As such, clusters are an optimization and |
| 246 | 246 | may be removed from a repository without loss or damage to the |
| 247 | 247 | underlying project code. |
| 248 | 248 | |
| 249 | 249 |
| --- www/fileformat.wiki | |
| +++ www/fileformat.wiki | |
| @@ -28,12 +28,12 @@ | |
| 28 | The local state is not composed of artifacts and is not intended to be enduring. |
| 29 | This document is concerned with global state only. Local state is only |
| 30 | mentioned here in order to distinguish it from global state. |
| 31 | |
| 32 | Each artifact in the repository is named by its SHA1 hash. |
| 33 | No prefixes or meta information is added to a artifact before |
| 34 | its hash is computed. The name of a artifact in the repository |
| 35 | is exactly the same SHA1 hash that is computed by sha1sum |
| 36 | on the file as it exists in your source tree.</p> |
| 37 | |
| 38 | Some artifacts have a particular format which gives them special |
| 39 | meaning to fossil. Fossil recognizes: |
| @@ -238,11 +238,11 @@ | |
| 238 | [/artifact/28987096ac | here]. |
| 239 | |
| 240 | <a name="cluster"></a> |
| 241 | <h2>2.0 Clusters</h2> |
| 242 | |
| 243 | A cluster is a artifact that declares the existence of other artifacts. |
| 244 | Clusters are used during repository synchronization to help |
| 245 | reduce network traffic. As such, clusters are an optimization and |
| 246 | may be removed from a repository without loss or damage to the |
| 247 | underlying project code. |
| 248 | |
| 249 |
| --- www/fileformat.wiki | |
| +++ www/fileformat.wiki | |
| @@ -28,12 +28,12 @@ | |
| 28 | The local state is not composed of artifacts and is not intended to be enduring. |
| 29 | This document is concerned with global state only. Local state is only |
| 30 | mentioned here in order to distinguish it from global state. |
| 31 | |
| 32 | Each artifact in the repository is named by its SHA1 hash. |
| 33 | No prefixes or meta information is added to an artifact before |
| 34 | its hash is computed. The name of an artifact in the repository |
| 35 | is exactly the same SHA1 hash that is computed by sha1sum |
| 36 | on the file as it exists in your source tree.</p> |
| 37 | |
| 38 | Some artifacts have a particular format which gives them special |
| 39 | meaning to fossil. Fossil recognizes: |
| @@ -238,11 +238,11 @@ | |
| 238 | [/artifact/28987096ac | here]. |
| 239 | |
| 240 | <a name="cluster"></a> |
| 241 | <h2>2.0 Clusters</h2> |
| 242 | |
| 243 | A cluster is an artifact that declares the existence of other artifacts. |
| 244 | Clusters are used during repository synchronization to help |
| 245 | reduce network traffic. As such, clusters are an optimization and |
| 246 | may be removed from a repository without loss or damage to the |
| 247 | underlying project code. |
| 248 | |
| 249 |
+1
-1
| --- www/pop.wiki | ||
| +++ www/pop.wiki | ||
| @@ -31,11 +31,11 @@ | ||
| 31 | 31 | In many contexts, the name can be |
| 32 | 32 | abbreviated to a unique prefix. A five- or six-character |
| 33 | 33 | prefix usually suffices to uniquely identify a file.</p></li> |
| 34 | 34 | |
| 35 | 35 | <li><p>Because artifacts are named by their SHA1 hash, all artifacts |
| 36 | -are immutable. Any change to the content of a artifact also | |
| 36 | +are immutable. Any change to the content of an artifact also | |
| 37 | 37 | changes the hash that forms the artifacts name, thus |
| 38 | 38 | creating a new artifact. Both the old original version of the |
| 39 | 39 | artifact and the new change are preserved under different names.</p></li> |
| 40 | 40 | |
| 41 | 41 | <li><p>It is theoretically possible for two artifacts with different |
| 42 | 42 |
| --- www/pop.wiki | |
| +++ www/pop.wiki | |
| @@ -31,11 +31,11 @@ | |
| 31 | In many contexts, the name can be |
| 32 | abbreviated to a unique prefix. A five- or six-character |
| 33 | prefix usually suffices to uniquely identify a file.</p></li> |
| 34 | |
| 35 | <li><p>Because artifacts are named by their SHA1 hash, all artifacts |
| 36 | are immutable. Any change to the content of a artifact also |
| 37 | changes the hash that forms the artifacts name, thus |
| 38 | creating a new artifact. Both the old original version of the |
| 39 | artifact and the new change are preserved under different names.</p></li> |
| 40 | |
| 41 | <li><p>It is theoretically possible for two artifacts with different |
| 42 |
| --- www/pop.wiki | |
| +++ www/pop.wiki | |
| @@ -31,11 +31,11 @@ | |
| 31 | In many contexts, the name can be |
| 32 | abbreviated to a unique prefix. A five- or six-character |
| 33 | prefix usually suffices to uniquely identify a file.</p></li> |
| 34 | |
| 35 | <li><p>Because artifacts are named by their SHA1 hash, all artifacts |
| 36 | are immutable. Any change to the content of an artifact also |
| 37 | changes the hash that forms the artifacts name, thus |
| 38 | creating a new artifact. Both the old original version of the |
| 39 | artifact and the new change are preserved under different names.</p></li> |
| 40 | |
| 41 | <li><p>It is theoretically possible for two artifacts with different |
| 42 |
+3
-3
| --- www/sync.wiki | ||
| +++ www/sync.wiki | ||
| @@ -447,14 +447,14 @@ | ||
| 447 | 447 | <p>If either the client or the server sees a card that is not |
| 448 | 448 | described above, then it generates an error and aborts.</p> |
| 449 | 449 | |
| 450 | 450 | <h2>4.0 Phantoms And Clusters</h2> |
| 451 | 451 | |
| 452 | -<p>When a repository knows that a artifact exists and knows the ID of | |
| 452 | +<p>When a repository knows that an artifact exists and knows the ID of | |
| 453 | 453 | that artifact, but it does not know the artifact content, then it stores that |
| 454 | 454 | artifact as a "phantom". A repository will typically create a phantom when |
| 455 | -it receives an igot card for a artifact that it does not hold or when it | |
| 455 | +it receives an igot card for an artifact that it does not hold or when it | |
| 456 | 456 | receives a file card that references a delta source that it does not |
| 457 | 457 | hold. When a server is generating its reply or when a client is |
| 458 | 458 | generating a new request, it will usually send gimme cards for every |
| 459 | 459 | phantom that it holds.</p> |
| 460 | 460 | |
| @@ -468,11 +468,11 @@ | ||
| 468 | 468 | single argument. No extra whitespace and no trailing or leading |
| 469 | 469 | whitespace is allowed. All cards in the cluster must occur in |
| 470 | 470 | strict lexicographical order.</p> |
| 471 | 471 | |
| 472 | 472 | <p>A cluster consists of one or more "M" cards followed by a single |
| 473 | -"Z" card. Each M card holds an argument which is a artifact ID for an | |
| 473 | +"Z" card. Each M card holds an argument which is an artifact ID for an | |
| 474 | 474 | artifact in the repository. The Z card has a single argument which is the |
| 475 | 475 | lower-case hexadecimal representation of the MD5 checksum of all |
| 476 | 476 | preceding M cards up to and included the newline character that |
| 477 | 477 | occurred just before the Z that starts the Z card.</p> |
| 478 | 478 | |
| 479 | 479 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -447,14 +447,14 @@ | |
| 447 | <p>If either the client or the server sees a card that is not |
| 448 | described above, then it generates an error and aborts.</p> |
| 449 | |
| 450 | <h2>4.0 Phantoms And Clusters</h2> |
| 451 | |
| 452 | <p>When a repository knows that a artifact exists and knows the ID of |
| 453 | that artifact, but it does not know the artifact content, then it stores that |
| 454 | artifact as a "phantom". A repository will typically create a phantom when |
| 455 | it receives an igot card for a artifact that it does not hold or when it |
| 456 | receives a file card that references a delta source that it does not |
| 457 | hold. When a server is generating its reply or when a client is |
| 458 | generating a new request, it will usually send gimme cards for every |
| 459 | phantom that it holds.</p> |
| 460 | |
| @@ -468,11 +468,11 @@ | |
| 468 | single argument. No extra whitespace and no trailing or leading |
| 469 | whitespace is allowed. All cards in the cluster must occur in |
| 470 | strict lexicographical order.</p> |
| 471 | |
| 472 | <p>A cluster consists of one or more "M" cards followed by a single |
| 473 | "Z" card. Each M card holds an argument which is a artifact ID for an |
| 474 | artifact in the repository. The Z card has a single argument which is the |
| 475 | lower-case hexadecimal representation of the MD5 checksum of all |
| 476 | preceding M cards up to and included the newline character that |
| 477 | occurred just before the Z that starts the Z card.</p> |
| 478 | |
| 479 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -447,14 +447,14 @@ | |
| 447 | <p>If either the client or the server sees a card that is not |
| 448 | described above, then it generates an error and aborts.</p> |
| 449 | |
| 450 | <h2>4.0 Phantoms And Clusters</h2> |
| 451 | |
| 452 | <p>When a repository knows that an artifact exists and knows the ID of |
| 453 | that artifact, but it does not know the artifact content, then it stores that |
| 454 | artifact as a "phantom". A repository will typically create a phantom when |
| 455 | it receives an igot card for an artifact that it does not hold or when it |
| 456 | receives a file card that references a delta source that it does not |
| 457 | hold. When a server is generating its reply or when a client is |
| 458 | generating a new request, it will usually send gimme cards for every |
| 459 | phantom that it holds.</p> |
| 460 | |
| @@ -468,11 +468,11 @@ | |
| 468 | single argument. No extra whitespace and no trailing or leading |
| 469 | whitespace is allowed. All cards in the cluster must occur in |
| 470 | strict lexicographical order.</p> |
| 471 | |
| 472 | <p>A cluster consists of one or more "M" cards followed by a single |
| 473 | "Z" card. Each M card holds an argument which is an artifact ID for an |
| 474 | artifact in the repository. The Z card has a single argument which is the |
| 475 | lower-case hexadecimal representation of the MD5 checksum of all |
| 476 | preceding M cards up to and included the newline character that |
| 477 | occurred just before the Z that starts the Z card.</p> |
| 478 | |
| 479 |