Fossil SCM
A few more tiny tweaks to the whyallinone.md doc.
Commit
1a74c2b38e0629636899318fbf6dbbb56da265b68dd8e319c826c31c41bf1873
Parent
2b76ea2b17d2076…
1 file changed
+2
-2
+2
-2
| --- www/whyallinone.md | ||
| +++ www/whyallinone.md | ||
| @@ -17,11 +17,11 @@ | ||
| 17 | 17 | |
| 18 | 18 | This commenter may hold whatever opinions he wishes, of course. |
| 19 | 19 | However, there are many good reasons why bundling other project management |
| 20 | 20 | features with the DVCS might be useful for a given project: |
| 21 | 21 | |
| 22 | - 1. There is single software package to install and manage for the | |
| 22 | + 1. There is a single software package to install and manage for the | |
| 23 | 23 | project website. |
| 24 | 24 | The alternative is to select, install, configure, learn about, |
| 25 | 25 | manage, and maintain separate DVCS, wiki, |
| 26 | 26 | ticketing, forum, |
| 27 | 27 | chat, documentation, and whatever other software packages your project needs. |
| @@ -35,11 +35,11 @@ | ||
| 35 | 35 | central server and have the developers clone that repository down |
| 36 | 36 | to their personal machines, if the server falls over, the last |
| 37 | 37 | developer to do anything that resulted in an autosync has a |
| 38 | 38 | functional and up-to-date backup. |
| 39 | 39 | |
| 40 | - There are [limitations to using Fossil’s autosync feature for | |
| 40 | + There are [limitations to relying on Fossil’s autosync feature for | |
| 41 | 41 | backup purposes](./backup.md), but that document gives two methods |
| 42 | 42 | for more complete backups, both of which are easily automated. The |
| 43 | 43 | Fossil project itself is distributed across three data centers in |
| 44 | 44 | this manner via cron. |
| 45 | 45 | |
| 46 | 46 |
| --- www/whyallinone.md | |
| +++ www/whyallinone.md | |
| @@ -17,11 +17,11 @@ | |
| 17 | |
| 18 | This commenter may hold whatever opinions he wishes, of course. |
| 19 | However, there are many good reasons why bundling other project management |
| 20 | features with the DVCS might be useful for a given project: |
| 21 | |
| 22 | 1. There is single software package to install and manage for the |
| 23 | project website. |
| 24 | The alternative is to select, install, configure, learn about, |
| 25 | manage, and maintain separate DVCS, wiki, |
| 26 | ticketing, forum, |
| 27 | chat, documentation, and whatever other software packages your project needs. |
| @@ -35,11 +35,11 @@ | |
| 35 | central server and have the developers clone that repository down |
| 36 | to their personal machines, if the server falls over, the last |
| 37 | developer to do anything that resulted in an autosync has a |
| 38 | functional and up-to-date backup. |
| 39 | |
| 40 | There are [limitations to using Fossil’s autosync feature for |
| 41 | backup purposes](./backup.md), but that document gives two methods |
| 42 | for more complete backups, both of which are easily automated. The |
| 43 | Fossil project itself is distributed across three data centers in |
| 44 | this manner via cron. |
| 45 | |
| 46 |
| --- www/whyallinone.md | |
| +++ www/whyallinone.md | |
| @@ -17,11 +17,11 @@ | |
| 17 | |
| 18 | This commenter may hold whatever opinions he wishes, of course. |
| 19 | However, there are many good reasons why bundling other project management |
| 20 | features with the DVCS might be useful for a given project: |
| 21 | |
| 22 | 1. There is a single software package to install and manage for the |
| 23 | project website. |
| 24 | The alternative is to select, install, configure, learn about, |
| 25 | manage, and maintain separate DVCS, wiki, |
| 26 | ticketing, forum, |
| 27 | chat, documentation, and whatever other software packages your project needs. |
| @@ -35,11 +35,11 @@ | |
| 35 | central server and have the developers clone that repository down |
| 36 | to their personal machines, if the server falls over, the last |
| 37 | developer to do anything that resulted in an autosync has a |
| 38 | functional and up-to-date backup. |
| 39 | |
| 40 | There are [limitations to relying on Fossil’s autosync feature for |
| 41 | backup purposes](./backup.md), but that document gives two methods |
| 42 | for more complete backups, both of which are easily automated. The |
| 43 | Fossil project itself is distributed across three data centers in |
| 44 | this manner via cron. |
| 45 | |
| 46 |