Fossil SCM
Use the term "structural artifacts" in place of the older "control artifact" notation.
Commit
1dda1b6df58b8f71df0eb394812800a5e3ab318c2d27b7cdba63412eda332e7e
Parent
f5240a1cb824f77…
1 file changed
+2
-2
+2
-2
| --- www/tech_overview.wiki | ||
| +++ www/tech_overview.wiki | ||
| @@ -6,12 +6,12 @@ | ||
| 6 | 6 | <h2>1.0 Introduction</h2> |
| 7 | 7 | |
| 8 | 8 | At its lowest level, a Fossil repository consists of an unordered set |
| 9 | 9 | of immutable "artifacts". You might think of these artifacts as "files", |
| 10 | 10 | since in many cases the artifacts are exactly that. |
| 11 | -But other "control artifacts" | |
| 12 | -are also included in the mix. These control artifacts define the relationships | |
| 11 | +But other "structural artifacts" are also included in the mix. | |
| 12 | +These structural artifacts define the relationships | |
| 13 | 13 | between artifacts - which files go together to form a particular |
| 14 | 14 | version of the project, who checked in that version and when, what was |
| 15 | 15 | the check-in comment, what wiki pages are included with the project, what |
| 16 | 16 | are the edit histories of each wiki page, what bug reports or tickets are |
| 17 | 17 | included, who contributed to the evolution of each ticket, and so forth. |
| 18 | 18 |
| --- www/tech_overview.wiki | |
| +++ www/tech_overview.wiki | |
| @@ -6,12 +6,12 @@ | |
| 6 | <h2>1.0 Introduction</h2> |
| 7 | |
| 8 | At its lowest level, a Fossil repository consists of an unordered set |
| 9 | of immutable "artifacts". You might think of these artifacts as "files", |
| 10 | since in many cases the artifacts are exactly that. |
| 11 | But other "control artifacts" |
| 12 | are also included in the mix. These control artifacts define the relationships |
| 13 | between artifacts - which files go together to form a particular |
| 14 | version of the project, who checked in that version and when, what was |
| 15 | the check-in comment, what wiki pages are included with the project, what |
| 16 | are the edit histories of each wiki page, what bug reports or tickets are |
| 17 | included, who contributed to the evolution of each ticket, and so forth. |
| 18 |
| --- www/tech_overview.wiki | |
| +++ www/tech_overview.wiki | |
| @@ -6,12 +6,12 @@ | |
| 6 | <h2>1.0 Introduction</h2> |
| 7 | |
| 8 | At its lowest level, a Fossil repository consists of an unordered set |
| 9 | of immutable "artifacts". You might think of these artifacts as "files", |
| 10 | since in many cases the artifacts are exactly that. |
| 11 | But other "structural artifacts" are also included in the mix. |
| 12 | These structural artifacts define the relationships |
| 13 | between artifacts - which files go together to form a particular |
| 14 | version of the project, who checked in that version and when, what was |
| 15 | the check-in comment, what wiki pages are included with the project, what |
| 16 | are the edit histories of each wiki page, what bug reports or tickets are |
| 17 | included, who contributed to the evolution of each ticket, and so forth. |
| 18 |