Documentation Source Text

Check-in [a41da69db7]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix a typo on the privatebranch.html page.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:a41da69db7f91867ee06ae0718087f76714bc14e2178ec9e9ed017f632ce2aa2
User & Date: drh 2018-01-25 16:06:11
Context
2018-01-26
15:44
Bring the query flattening section of the optoverview.html document up to date with version 3.22.0. check-in: a599e76d95 user: drh tags: trunk
2018-01-25
16:06
Fix a typo on the privatebranch.html page. check-in: a41da69db7 user: drh tags: trunk
12:25
Fix hyperlink errors in the sqlanalyze.html page. check-in: 7941cd31c2 user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/privatebranch.in.

355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
simply by cloning the official repository:</p>

<blockquote><pre>
fossil clone http://www.sqlite.org/src private-project.fossil
</pre></blockquote>

<p>This command both creates the new repository and populates it with
all the latest SQLite could.  You can then create a private branch as
described in section 3.4.</p>

<p>When the private repository is created by cloning, incorporating new
public SQLite releases becomes much easier too.  To pull in all of the
latest changes from the public SQLite repository, simply move into
the open check-out and do:</p>

<blockquote><pre>
fossil update
</pre></blockquote>

<p>Then continue to merge the changes in "trunk" with your "private"
changes as described in section 3.7.</p>







|













355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
simply by cloning the official repository:</p>

<blockquote><pre>
fossil clone http://www.sqlite.org/src private-project.fossil
</pre></blockquote>

<p>This command both creates the new repository and populates it with
all the latest SQLite code.  You can then create a private branch as
described in section 3.4.</p>

<p>When the private repository is created by cloning, incorporating new
public SQLite releases becomes much easier too.  To pull in all of the
latest changes from the public SQLite repository, simply move into
the open check-out and do:</p>

<blockquote><pre>
fossil update
</pre></blockquote>

<p>Then continue to merge the changes in "trunk" with your "private"
changes as described in section 3.7.</p>