Fossil SCM
Fix a minor formatting error in the alerts.md document.
Commit
6ec931a13db1b0f9c030e6c8937cc633d6cf5944df37bde2cb5ceef4c4441109
Parent
a0ae0c9ff660fba…
1 file changed
+2
-2
+2
-2
| --- www/alerts.md | ||
| +++ www/alerts.md | ||
| @@ -718,12 +718,12 @@ | ||
| 718 | 718 | Almost all of the email alert code is found in the |
| 719 | 719 | [`src/alerts.c`](/file/src/alerts.c) source file. |
| 720 | 720 | |
| 721 | 721 | When email alerts are enabled, a trigger is created in the schema |
| 722 | 722 | (`email_trigger1`) that adds a new entry to the `PENDING_ALERT` table |
| 723 | -every time a row is added to the `EVENT` table. During a `fossil | |
| 724 | -rebuild`, the `EVENT` table is rebuilt from scratch; since we do not | |
| 723 | +every time a row is added to the `EVENT` table. During a | |
| 724 | +`fossil rebuild`, the `EVENT` table is rebuilt from scratch; since we do not | |
| 725 | 725 | want users to get alerts for every historical check-in, the trigger is |
| 726 | 726 | disabled during `rebuild`. |
| 727 | 727 | |
| 728 | 728 | Email alerts are sent out by the `alert_send_alerts()` function, which |
| 729 | 729 | is normally called automatically due to the `email-autoexec` setting, |
| 730 | 730 |
| --- www/alerts.md | |
| +++ www/alerts.md | |
| @@ -718,12 +718,12 @@ | |
| 718 | Almost all of the email alert code is found in the |
| 719 | [`src/alerts.c`](/file/src/alerts.c) source file. |
| 720 | |
| 721 | When email alerts are enabled, a trigger is created in the schema |
| 722 | (`email_trigger1`) that adds a new entry to the `PENDING_ALERT` table |
| 723 | every time a row is added to the `EVENT` table. During a `fossil |
| 724 | rebuild`, the `EVENT` table is rebuilt from scratch; since we do not |
| 725 | want users to get alerts for every historical check-in, the trigger is |
| 726 | disabled during `rebuild`. |
| 727 | |
| 728 | Email alerts are sent out by the `alert_send_alerts()` function, which |
| 729 | is normally called automatically due to the `email-autoexec` setting, |
| 730 |
| --- www/alerts.md | |
| +++ www/alerts.md | |
| @@ -718,12 +718,12 @@ | |
| 718 | Almost all of the email alert code is found in the |
| 719 | [`src/alerts.c`](/file/src/alerts.c) source file. |
| 720 | |
| 721 | When email alerts are enabled, a trigger is created in the schema |
| 722 | (`email_trigger1`) that adds a new entry to the `PENDING_ALERT` table |
| 723 | every time a row is added to the `EVENT` table. During a |
| 724 | `fossil rebuild`, the `EVENT` table is rebuilt from scratch; since we do not |
| 725 | want users to get alerts for every historical check-in, the trigger is |
| 726 | disabled during `rebuild`. |
| 727 | |
| 728 | Email alerts are sent out by the `alert_send_alerts()` function, which |
| 729 | is normally called automatically due to the `email-autoexec` setting, |
| 730 |