Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Update the README.md file at the top of the repository so that the homepage of Git mirrors of SQLite direct users to the official repository. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
08f11980efa907728102065115a5bebd |
| User & Date: | drh 2015-05-15 22:20:40.611 |
Context
|
2015-05-16
| ||
| 03:41 | Improve the clean target in the MSVC makefile. (check-in: 2c1039d454 user: mistachkin tags: trunk) | |
|
2015-05-15
| ||
| 22:20 | Update the README.md file at the top of the repository so that the homepage of Git mirrors of SQLite direct users to the official repository. (check-in: 08f11980ef user: drh tags: trunk) | |
| 20:14 | Minor coding style change, adjust new local variable casing for consistency. (check-in: 1a4628c66c user: mistachkin tags: trunk) | |
Changes
Changes to README.md.
1 2 3 4 5 6 7 8 9 10 11 12 | <h1 align="center">SQLite Source Repository</h1> This repository contains the complete source code for the SQLite database engine. Some test scripts are also include. However, many other test scripts and most of the documentation are managed separately. ## Compiling First create a directory in which to place the build products. It is recommended, but not required, that the build directory be separate from the source directory. Cd into the build directory and then from the build directory run the configure | > > > > | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | <h1 align="center">SQLite Source Repository</h1> This repository contains the complete source code for the SQLite database engine. Some test scripts are also include. However, many other test scripts and most of the documentation are managed separately. If you are reading this on a Git mirror someplace, you are doing it wrong. The [official repository](https://www.sqlite.org/src/) is better. Go there now. ## Compiling First create a directory in which to place the build products. It is recommended, but not required, that the build directory be separate from the source directory. Cd into the build directory and then from the build directory run the configure |
| ︙ | ︙ |