Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
|Comment:||New hyperlink on the README.md file.|
|Downloads:||Tarball | ZIP archive | SQL archive|
|Timelines:||family | ancestors | descendants | both | trunk|
|Files:||files | file ages | folders|
|User & Date:||drh 2019-03-17 23:59:02|
|10:30||Fix a typo in a comment. No changes to code. (check-in: c2f50aa4 user: drh tags: trunk)|
|23:59||New hyperlink on the README.md file. (check-in: cc5ab967 user: drh tags: trunk)|
|23:44||Update the README.md file at the top level to talk about how to deal with version names and how to verify the code in Git mirrors. (check-in: e8c87a0a user: drh tags: trunk)|
Changes to README.md.
6 6 and most of the documentation are managed separately. 7 7 8 8 ## Version Control 9 9 10 10 SQLite sources are managed using the 11 11 [Fossil](https://www.fossil-scm.org/), a distributed version control system 12 12 that was specifically designed and written to support SQLite development. 13 -The Fossil repository contains the urtext. 13 +The [Fossil repository](https://sqlite.org/src/timeline) contains the urtext. 14 14 15 15 If you are reading this on GitHub or some other Git repository or service, 16 16 then you are looking at a mirror. The names of check-ins and 17 17 other artifacts in a Git mirror are different from the official 18 18 names for those objects. The offical names for check-ins are 19 19 found in a footer on the check-in comment for authorized mirrors. 20 20 The official check-in name can also be seen in the `manifest.uuid` file