Fossil SCM
(Grammar) glossary.md changes.
Commit
248e05a7e1e462b68ad49ba1dcb5dfb7a7780a744e4b8512423c7f297ed950f7
Parent
6bd9009d72c87ac…
1 file changed
+1
-1
+1
-1
| --- www/glossary.md | ||
| +++ www/glossary.md | ||
| @@ -73,11 +73,11 @@ | ||
| 73 | 73 | because you’ll have all of your OS’s *other* files intermixed. |
| 74 | 74 | Worse, Fossil doesn’t track OS permissions, so even if you were to |
| 75 | 75 | try to use Fossil as a system deployment tool by archiving versions |
| 76 | 76 | of the OS configuration files and then unpacking them on a new |
| 77 | 77 | system, the extracted project files would have read/write access by |
| 78 | - the user who did the extraction, which probably isn’t want you were | |
| 78 | + the user who did the extraction, which probably isn’t what you were | |
| 79 | 79 | wanting. |
| 80 | 80 | |
| 81 | 81 | Even with these problems aside, do you really want a `.fslckout` |
| 82 | 82 | SQLite database at the root of your filesystem? Are you prepared for |
| 83 | 83 | the consequences of saying `fossil clean --verily` on such a system? |
| 84 | 84 |
| --- www/glossary.md | |
| +++ www/glossary.md | |
| @@ -73,11 +73,11 @@ | |
| 73 | because you’ll have all of your OS’s *other* files intermixed. |
| 74 | Worse, Fossil doesn’t track OS permissions, so even if you were to |
| 75 | try to use Fossil as a system deployment tool by archiving versions |
| 76 | of the OS configuration files and then unpacking them on a new |
| 77 | system, the extracted project files would have read/write access by |
| 78 | the user who did the extraction, which probably isn’t want you were |
| 79 | wanting. |
| 80 | |
| 81 | Even with these problems aside, do you really want a `.fslckout` |
| 82 | SQLite database at the root of your filesystem? Are you prepared for |
| 83 | the consequences of saying `fossil clean --verily` on such a system? |
| 84 |
| --- www/glossary.md | |
| +++ www/glossary.md | |
| @@ -73,11 +73,11 @@ | |
| 73 | because you’ll have all of your OS’s *other* files intermixed. |
| 74 | Worse, Fossil doesn’t track OS permissions, so even if you were to |
| 75 | try to use Fossil as a system deployment tool by archiving versions |
| 76 | of the OS configuration files and then unpacking them on a new |
| 77 | system, the extracted project files would have read/write access by |
| 78 | the user who did the extraction, which probably isn’t what you were |
| 79 | wanting. |
| 80 | |
| 81 | Even with these problems aside, do you really want a `.fslckout` |
| 82 | SQLite database at the root of your filesystem? Are you prepared for |
| 83 | the consequences of saying `fossil clean --verily` on such a system? |
| 84 |