Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix a typo in the whynotgit.html document. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
44fe2354a149f2ea83d982844f246a10 |
| User & Date: | drh 2018-04-10 17:09:22 |
Context
|
2018-04-10
| ||
| 17:44 | Version 3.23.1 check-in: f7fce883af user: drh tags: trunk, release, version-3.23.1 | |
| 17:09 | Fix a typo in the whynotgit.html document. check-in: 44fe2354a1 user: drh tags: trunk | |
| 13:48 | Update the performance and size spreadsheet. Update the cpu.html page with the latest graph. check-in: 9e3acfbfab user: drh tags: trunk | |
Changes
Changes to pages/whynotgit.in.
6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
<p>
SQLite does not use the
[https://git-scm.org|Git] version control system.
SQLite uses
[https://fossil-scm.org/|Fossil] instead.
Fossil and Git are both block-chain version-control systems.
They are both "distributed". They both store content has a
sequence of immutable check-ins identified by a cryptographic
hash. Git is wildly popular, to the point that many younger
developers are familiar with nothing else. And yet, the developers
of SQLite prefer Fossil. This article tries to explain why.
<h1>A Few Reasons Why SQLite Does Not Use Git</h1>
|
| |
6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
<p> SQLite does not use the [https://git-scm.org|Git] version control system. SQLite uses [https://fossil-scm.org/|Fossil] instead. Fossil and Git are both block-chain version-control systems. They are both "distributed". They both store content as a sequence of immutable check-ins identified by a cryptographic hash. Git is wildly popular, to the point that many younger developers are familiar with nothing else. And yet, the developers of SQLite prefer Fossil. This article tries to explain why. <h1>A Few Reasons Why SQLite Does Not Use Git</h1> |