Fossil SCM
Replaced the WIP and indefinite future paragraphs in www/alerts.md with definite statements now that we're approaching release.
Commit
05b40829151aa8a56a6b6ab98b3f89b0c1c8e9b6037a0c346b36abcd4c745a19
Parent
edc31f4691c5e12…
1 file changed
+2
-6
+2
-6
| --- www/alerts.md | ||
| +++ www/alerts.md | ||
| @@ -1,12 +1,8 @@ | ||
| 1 | 1 | Email Alerts |
| 2 | 2 | ============ |
| 3 | 3 | |
| 4 | -The email alert system is a work-in-progress. | |
| 5 | -This documentation was last updated on 2018-08-12. | |
| 6 | -Check back later for updates. | |
| 7 | - | |
| 8 | 4 | Email Alerts And Notifications |
| 9 | 5 | ------------------------------ |
| 10 | 6 | |
| 11 | 7 | Beginning with version 2.7, Fossil supports the ability to send |
| 12 | 8 | email messages to subscribers alerting them to changes in the repository. |
| @@ -69,12 +65,12 @@ | ||
| 69 | 65 | 3. Store email messages as entries in an SQLite database where |
| 70 | 66 | some external process and read and forward the emails. |
| 71 | 67 | 4. Send emails to an SMTP Relay. |
| 72 | 68 | 5. Send emails directly to the recipients via SMTP. |
| 73 | 69 | |
| 74 | -As of 2018-08-08, method (5) is not yet supported, but there are plans | |
| 75 | -to add support soon. | |
| 70 | +Fossil 2.7 does not support method (5). Work on supporting that method | |
| 71 | +is still in progress. | |
| 76 | 72 | |
| 77 | 73 | The self-hosting Fossil repository at <https://www.fossil-scm.org/> currently |
| 78 | 74 | uses method (3). Outgoing email messages are added to an SQLite database |
| 79 | 75 | file. A separate daemon process continously monitors that database file, |
| 80 | 76 | extracts email messages as they are added, and hands them off to |
| 81 | 77 |
| --- www/alerts.md | |
| +++ www/alerts.md | |
| @@ -1,12 +1,8 @@ | |
| 1 | Email Alerts |
| 2 | ============ |
| 3 | |
| 4 | The email alert system is a work-in-progress. |
| 5 | This documentation was last updated on 2018-08-12. |
| 6 | Check back later for updates. |
| 7 | |
| 8 | Email Alerts And Notifications |
| 9 | ------------------------------ |
| 10 | |
| 11 | Beginning with version 2.7, Fossil supports the ability to send |
| 12 | email messages to subscribers alerting them to changes in the repository. |
| @@ -69,12 +65,12 @@ | |
| 69 | 3. Store email messages as entries in an SQLite database where |
| 70 | some external process and read and forward the emails. |
| 71 | 4. Send emails to an SMTP Relay. |
| 72 | 5. Send emails directly to the recipients via SMTP. |
| 73 | |
| 74 | As of 2018-08-08, method (5) is not yet supported, but there are plans |
| 75 | to add support soon. |
| 76 | |
| 77 | The self-hosting Fossil repository at <https://www.fossil-scm.org/> currently |
| 78 | uses method (3). Outgoing email messages are added to an SQLite database |
| 79 | file. A separate daemon process continously monitors that database file, |
| 80 | extracts email messages as they are added, and hands them off to |
| 81 |
| --- www/alerts.md | |
| +++ www/alerts.md | |
| @@ -1,12 +1,8 @@ | |
| 1 | Email Alerts |
| 2 | ============ |
| 3 | |
| 4 | Email Alerts And Notifications |
| 5 | ------------------------------ |
| 6 | |
| 7 | Beginning with version 2.7, Fossil supports the ability to send |
| 8 | email messages to subscribers alerting them to changes in the repository. |
| @@ -69,12 +65,12 @@ | |
| 65 | 3. Store email messages as entries in an SQLite database where |
| 66 | some external process and read and forward the emails. |
| 67 | 4. Send emails to an SMTP Relay. |
| 68 | 5. Send emails directly to the recipients via SMTP. |
| 69 | |
| 70 | Fossil 2.7 does not support method (5). Work on supporting that method |
| 71 | is still in progress. |
| 72 | |
| 73 | The self-hosting Fossil repository at <https://www.fossil-scm.org/> currently |
| 74 | uses method (3). Outgoing email messages are added to an SQLite database |
| 75 | file. A separate daemon process continously monitors that database file, |
| 76 | extracts email messages as they are added, and hands them off to |
| 77 |