Fossil SCM
(Typos) tickets.wiki changes.
Commit
bf5118059b20b12085fd6eea839273d861c16a1c9abc5598fd78836204f2f4c4
Parent
e2c79bb90e2f533…
1 file changed
+2
-2
+2
-2
| --- www/tickets.wiki | ||
| +++ www/tickets.wiki | ||
| @@ -27,11 +27,11 @@ | ||
| 27 | 27 | that key, or the value may be appended to the prior value. |
| 28 | 28 | |
| 29 | 29 | <h2>2.0 Ticket Tables</h2> |
| 30 | 30 | |
| 31 | 31 | The low-level artifact format for ticket content is tedious and |
| 32 | -cumbersome to access in real time. To facility reporting and display | |
| 32 | +cumbersome to access in real time. To facilitate reporting and display | |
| 33 | 33 | of tickets, the low-level artifact information is collected and |
| 34 | 34 | summarized in a pair of SQL tables in each local repository. Display |
| 35 | 35 | and reporting of tickets is accomplished by querying these two tables. |
| 36 | 36 | |
| 37 | 37 | Note that only the low-level ticket change artifacts are synced. The |
| @@ -191,9 +191,9 @@ | ||
| 191 | 191 | comment according to its chosen format. Hence, Fossil was enhanced to |
| 192 | 192 | support the "new-style" tickets. |
| 193 | 193 | |
| 194 | 194 | The TICKETCHNG table was added to support new-style tickets. In the new |
| 195 | 195 | style, comment text is stored with the "icomment" (for "Incremental Comment") |
| 196 | -key and appears separately, and with its on mimetype, in multiple rows | |
| 196 | +key and appears separately, and with its own mimetype, in multiple rows | |
| 197 | 197 | of the TICKETCHNG table. It then falls to the TH1 script code on the |
| 198 | 198 | View Ticket Page to query the TICKETCHNG table and extract and format |
| 199 | 199 | the various comments in time stamp order. |
| 200 | 200 |
| --- www/tickets.wiki | |
| +++ www/tickets.wiki | |
| @@ -27,11 +27,11 @@ | |
| 27 | that key, or the value may be appended to the prior value. |
| 28 | |
| 29 | <h2>2.0 Ticket Tables</h2> |
| 30 | |
| 31 | The low-level artifact format for ticket content is tedious and |
| 32 | cumbersome to access in real time. To facility reporting and display |
| 33 | of tickets, the low-level artifact information is collected and |
| 34 | summarized in a pair of SQL tables in each local repository. Display |
| 35 | and reporting of tickets is accomplished by querying these two tables. |
| 36 | |
| 37 | Note that only the low-level ticket change artifacts are synced. The |
| @@ -191,9 +191,9 @@ | |
| 191 | comment according to its chosen format. Hence, Fossil was enhanced to |
| 192 | support the "new-style" tickets. |
| 193 | |
| 194 | The TICKETCHNG table was added to support new-style tickets. In the new |
| 195 | style, comment text is stored with the "icomment" (for "Incremental Comment") |
| 196 | key and appears separately, and with its on mimetype, in multiple rows |
| 197 | of the TICKETCHNG table. It then falls to the TH1 script code on the |
| 198 | View Ticket Page to query the TICKETCHNG table and extract and format |
| 199 | the various comments in time stamp order. |
| 200 |
| --- www/tickets.wiki | |
| +++ www/tickets.wiki | |
| @@ -27,11 +27,11 @@ | |
| 27 | that key, or the value may be appended to the prior value. |
| 28 | |
| 29 | <h2>2.0 Ticket Tables</h2> |
| 30 | |
| 31 | The low-level artifact format for ticket content is tedious and |
| 32 | cumbersome to access in real time. To facilitate reporting and display |
| 33 | of tickets, the low-level artifact information is collected and |
| 34 | summarized in a pair of SQL tables in each local repository. Display |
| 35 | and reporting of tickets is accomplished by querying these two tables. |
| 36 | |
| 37 | Note that only the low-level ticket change artifacts are synced. The |
| @@ -191,9 +191,9 @@ | |
| 191 | comment according to its chosen format. Hence, Fossil was enhanced to |
| 192 | support the "new-style" tickets. |
| 193 | |
| 194 | The TICKETCHNG table was added to support new-style tickets. In the new |
| 195 | style, comment text is stored with the "icomment" (for "Incremental Comment") |
| 196 | key and appears separately, and with its own mimetype, in multiple rows |
| 197 | of the TICKETCHNG table. It then falls to the TH1 script code on the |
| 198 | View Ticket Page to query the TICKETCHNG table and extract and format |
| 199 | the various comments in time stamp order. |
| 200 |