Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix a typo in the privatebranch.html document. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
04a7a8e7ddff8420f3af83cbf9f16194 |
| User & Date: | drh 2009-12-15 14:05:21 |
Context
|
2009-12-15
| ||
| 14:34 | Clean up and extend the privatebranch.html document. check-in: b44ff2a454 user: drh tags: trunk | |
| 14:05 | Fix a typo in the privatebranch.html document. check-in: 04a7a8e7dd user: drh tags: trunk | |
| 00:29 | Add requirements markings to the pragma documentation. check-in: a900d49554 user: drh tags: trunk | |
Changes
Changes to pages/privatebranch.in.
154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 |
<p>You can have multiple checkouts of the same project if you want.
And you can "clone" the repository to different machines so that multiple
developers can use it. See the fossil website for further information.</p>
<h2>3.3 Installing The SQLite Baseline In Fossil</h2>
<p>The repository created in the previous set is initially empty. The
next step is to load the baseline SQLite release - circle (1) in the diagram
above.</p>
<p>Begin by obtaining a copy of SQLite in whatever form you use it.
The public SQLite you obtain should be as close to your private edited
copy as possible. If your project uses the SQLite amalgamation, then
get a copy of the the amalgamation. If you use the preprocessed separate
|
| |
154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 |
<p>You can have multiple checkouts of the same project if you want.
And you can "clone" the repository to different machines so that multiple
developers can use it. See the fossil website for further information.</p>
<h2>3.3 Installing The SQLite Baseline In Fossil</h2>
<p>The repository created in the previous step is initially empty. The
next step is to load the baseline SQLite release - circle (1) in the diagram
above.</p>
<p>Begin by obtaining a copy of SQLite in whatever form you use it.
The public SQLite you obtain should be as close to your private edited
copy as possible. If your project uses the SQLite amalgamation, then
get a copy of the the amalgamation. If you use the preprocessed separate
|