Fossil SCM
Typo fix in fossil-v-git.wiki
Commit
2a4322d8fd554787a11e07295d3e737d1a597f09d91a2248a6e5c1a5e5df25f7
Parent
77377e6c021534c…
1 file changed
+1
-1
+1
-1
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -232,11 +232,11 @@ | ||
| 232 | 232 | formatting details. Both systems manage a |
| 233 | 233 | [https://en.wikipedia.org/wiki/Directed_acyclic_graph | directed acyclic |
| 234 | 234 | graph] (DAG) of [https://en.wikipedia.org/wiki/Merkle_tree | Merkle |
| 235 | 235 | tree] / [./blockchain.md | block chain] structured check-in objects. |
| 236 | 236 | Check-ins are identified by a cryptographic hash of the check-in |
| 237 | -comment, and each check-in refers to its parent via <i>its</i> hash. | |
| 237 | +contents, and each check-in refers to its parent via <i>its</i> hash. | |
| 238 | 238 | |
| 239 | 239 | The difference is that Git stores its objects as individual files in the |
| 240 | 240 | <tt>.git</tt> folder or compressed into bespoke |
| 241 | 241 | [https://git-scm.com/book/en/v2/Git-Internals-Packfiles|pack-files], |
| 242 | 242 | whereas Fossil stores its objects in a [https://www.sqlite.org/|SQLite] |
| 243 | 243 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -232,11 +232,11 @@ | |
| 232 | formatting details. Both systems manage a |
| 233 | [https://en.wikipedia.org/wiki/Directed_acyclic_graph | directed acyclic |
| 234 | graph] (DAG) of [https://en.wikipedia.org/wiki/Merkle_tree | Merkle |
| 235 | tree] / [./blockchain.md | block chain] structured check-in objects. |
| 236 | Check-ins are identified by a cryptographic hash of the check-in |
| 237 | comment, and each check-in refers to its parent via <i>its</i> hash. |
| 238 | |
| 239 | The difference is that Git stores its objects as individual files in the |
| 240 | <tt>.git</tt> folder or compressed into bespoke |
| 241 | [https://git-scm.com/book/en/v2/Git-Internals-Packfiles|pack-files], |
| 242 | whereas Fossil stores its objects in a [https://www.sqlite.org/|SQLite] |
| 243 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -232,11 +232,11 @@ | |
| 232 | formatting details. Both systems manage a |
| 233 | [https://en.wikipedia.org/wiki/Directed_acyclic_graph | directed acyclic |
| 234 | graph] (DAG) of [https://en.wikipedia.org/wiki/Merkle_tree | Merkle |
| 235 | tree] / [./blockchain.md | block chain] structured check-in objects. |
| 236 | Check-ins are identified by a cryptographic hash of the check-in |
| 237 | contents, and each check-in refers to its parent via <i>its</i> hash. |
| 238 | |
| 239 | The difference is that Git stores its objects as individual files in the |
| 240 | <tt>.git</tt> folder or compressed into bespoke |
| 241 | [https://git-scm.com/book/en/v2/Git-Internals-Packfiles|pack-files], |
| 242 | whereas Fossil stores its objects in a [https://www.sqlite.org/|SQLite] |
| 243 |