Differences From:
File www/bugtheory.wiki part of check-in [e8c4f69c50] - Change all mentions of "UUID" in the documentation and help screens into either "artifact ID" or "baseline ID" or "ticket ID" as appropriate. "UUID" has a widely recognized meaning that is different from its meaning in fossil. "UUID" is still used in code comments and in variable names. by drh on 2008-10-24 13:27:53. [view]
To:
File www/bugtheory.wiki part of check-in [9eb6ea75c1] - doc changes -- spelling corrections and embedded ref pages. by kejoki on 2008-11-11 03:50:39. [view]
@@ -80,9 +80,9 @@ artifact is off by months or years, it can seriously confuse the replay algorithm for determining the current ticket state. There are techniques available to cause rogue artifacts to be ignored by fossil. So if a ticket change artifact with a bad timestamp -does get into a repository, it can be removed by an adminstrator. +does get into a repository, it can be removed by an administrator. But the best approach is to take steps to insure that timestamps are approximately correct in the first place. <h2>Local Configuration</h2> @@ -103,19 +103,19 @@ in the TICKET table, then that name/value pair is ignored. Columns can be added or removed from the TICKET table at any time. Whenever the TICKET table is modified, the replay algorithm automatically reruns to repopulate the table using the new column names. Note that the TICKET -table schema and content is part of the local state of a respository +table schema and content is part of the local state of a repository and is not shared with other repositories during a sync, push, or pull. Each repository also defines scripts used to generate web pages for creating new tickets, viewing existing tickets, and modifying an existing ticket. These scripts consist of HTML with an embedded -scripts written an a TCL-like language called "TH1". Every new fossil +scripts written an a Tcl-like language called "TH1". Every new fossil repository is created with default scripts. There is currently no -documentation on the TH1 langauage. Administrators wishing to +documentation on the TH1 language. Administrators wishing to customize their ticket entry, viewing, and editing screens should modify the default scripts to suit their needs. These screen generator scripts are part of the local state of a repository and are not shared with other repositories during a sync, push, or pull. <i>To be continued...</i>