Fossil SCM
The chat doc was using blockquote MD markup for code examples, making them look different from all the others.
Commit
d6dff8d714e645d9f2e03512429ba525d16202104bc2f3eccef011fe08e2f67e
Parent
ea3925bdc146754…
1 file changed
+2
-2
+2
-2
| --- www/chat.md | ||
| +++ www/chat.md | ||
| @@ -146,11 +146,11 @@ | ||
| 146 | 146 | the "C" privilege only. That means that the robot user account will be |
| 147 | 147 | able to send chat messages, but not do anything else. Then, in the |
| 148 | 148 | program or script that runs the robot, when it wants to send a chat |
| 149 | 149 | message, have it run a command like this: |
| 150 | 150 | |
| 151 | -> ~~~~ | |
| 151 | +~~~~ | |
| 152 | 152 | fossil chat send --remote https://robot:[email protected]/fossil \ |
| 153 | 153 | --message 'MESSAGE TEXT' --file file-to-attach.txt |
| 154 | 154 | ~~~~ |
| 155 | 155 | |
| 156 | 156 | Substitute the appropriate project URL, robot account |
| @@ -212,11 +212,11 @@ | ||
| 212 | 212 | files and via inlined image tags. |
| 213 | 213 | |
| 214 | 214 | Chat messages are stored on the server-side in the CHAT table of |
| 215 | 215 | the repository. |
| 216 | 216 | |
| 217 | -> ~~~ | |
| 217 | +~~~ | |
| 218 | 218 | CREATE TABLE repository.chat( |
| 219 | 219 | msgid INTEGER PRIMARY KEY AUTOINCREMENT, |
| 220 | 220 | mtime JULIANDAY, -- Time for this entry - Julianday Zulu |
| 221 | 221 | lmtime TEXT, -- Client YYYY-MM-DDZHH:MM:SS when message originally sent |
| 222 | 222 | xfrom TEXT, -- Login of the sender |
| 223 | 223 |
| --- www/chat.md | |
| +++ www/chat.md | |
| @@ -146,11 +146,11 @@ | |
| 146 | the "C" privilege only. That means that the robot user account will be |
| 147 | able to send chat messages, but not do anything else. Then, in the |
| 148 | program or script that runs the robot, when it wants to send a chat |
| 149 | message, have it run a command like this: |
| 150 | |
| 151 | > ~~~~ |
| 152 | fossil chat send --remote https://robot:[email protected]/fossil \ |
| 153 | --message 'MESSAGE TEXT' --file file-to-attach.txt |
| 154 | ~~~~ |
| 155 | |
| 156 | Substitute the appropriate project URL, robot account |
| @@ -212,11 +212,11 @@ | |
| 212 | files and via inlined image tags. |
| 213 | |
| 214 | Chat messages are stored on the server-side in the CHAT table of |
| 215 | the repository. |
| 216 | |
| 217 | > ~~~ |
| 218 | CREATE TABLE repository.chat( |
| 219 | msgid INTEGER PRIMARY KEY AUTOINCREMENT, |
| 220 | mtime JULIANDAY, -- Time for this entry - Julianday Zulu |
| 221 | lmtime TEXT, -- Client YYYY-MM-DDZHH:MM:SS when message originally sent |
| 222 | xfrom TEXT, -- Login of the sender |
| 223 |
| --- www/chat.md | |
| +++ www/chat.md | |
| @@ -146,11 +146,11 @@ | |
| 146 | the "C" privilege only. That means that the robot user account will be |
| 147 | able to send chat messages, but not do anything else. Then, in the |
| 148 | program or script that runs the robot, when it wants to send a chat |
| 149 | message, have it run a command like this: |
| 150 | |
| 151 | ~~~~ |
| 152 | fossil chat send --remote https://robot:[email protected]/fossil \ |
| 153 | --message 'MESSAGE TEXT' --file file-to-attach.txt |
| 154 | ~~~~ |
| 155 | |
| 156 | Substitute the appropriate project URL, robot account |
| @@ -212,11 +212,11 @@ | |
| 212 | files and via inlined image tags. |
| 213 | |
| 214 | Chat messages are stored on the server-side in the CHAT table of |
| 215 | the repository. |
| 216 | |
| 217 | ~~~ |
| 218 | CREATE TABLE repository.chat( |
| 219 | msgid INTEGER PRIMARY KEY AUTOINCREMENT, |
| 220 | mtime JULIANDAY, -- Time for this entry - Julianday Zulu |
| 221 | lmtime TEXT, -- Client YYYY-MM-DDZHH:MM:SS when message originally sent |
| 222 | xfrom TEXT, -- Login of the sender |
| 223 |