Fossil

Check-in [1dda1b6d]
Login

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

Overview
Comment:Use the term "structural artifacts" in place of the older "control artifact" notation.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 1dda1b6df58b8f71df0eb394812800a5e3ab318c2d27b7cdba63412eda332e7e
User & Date: drh 2017-03-12 18:59:09
Context
2017-03-12
23:32
More refactoring of "control artifact" to "structural artifact". Also improve the wording. All in the selfcheck document. check-in: 43c3d95a user: drh tags: trunk
18:59
Use the term "structural artifacts" in place of the older "control artifact" notation. check-in: 1dda1b6d user: drh tags: trunk
17:01
More hyperlink fixes on the same page. check-in: f5240a1c user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/tech_overview.wiki.

4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
</h2>

<h2>1.0 Introduction</h2>

At its lowest level, a Fossil repository consists of an unordered set
of immutable "artifacts".  You might think of these artifacts as "files",
since in many cases the artifacts are exactly that.
But other "control artifacts"
are also included in the mix.  These control artifacts define the relationships
between artifacts - which files go together to form a particular
version of the project, who checked in that version and when, what was
the check-in comment, what wiki pages are included with the project, what
are the edit histories of each wiki page, what bug reports or tickets are
included, who contributed to the evolution of each ticket, and so forth.
This low-level file format is called the "global state" of
the repository, since this is the information that is synced to peer







|
|







4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
</h2>

<h2>1.0 Introduction</h2>

At its lowest level, a Fossil repository consists of an unordered set
of immutable "artifacts".  You might think of these artifacts as "files",
since in many cases the artifacts are exactly that.
But other "structural artifacts" are also included in the mix.
These structural artifacts define the relationships
between artifacts - which files go together to form a particular
version of the project, who checked in that version and when, what was
the check-in comment, what wiki pages are included with the project, what
are the edit histories of each wiki page, what bug reports or tickets are
included, who contributed to the evolution of each ticket, and so forth.
This low-level file format is called the "global state" of
the repository, since this is the information that is synced to peer