Fossil SCM
More typos in the fossil-v-git document.
Commit
a17ed85c08993b4e225e7b80f54c959f22718242
Parent
328fc92ceb31827…
1 file changed
+5
-5
+5
-5
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -72,15 +72,15 @@ | ||
| 72 | 72 | at a time. Git encourages a programming model where each developer |
| 73 | 73 | works in his or her own branch and then merges changes up the hierarchy |
| 74 | 74 | until they reach the master branch. |
| 75 | 75 | |
| 76 | 76 | Fossil is designed for smaller and non-hierarchical teams where all |
| 77 | -developers are operating directly on the master branch, or at most one | |
| 77 | +developers are operating directly on the master branch, or at most | |
| 78 | 78 | a small number of well defined branches. |
| 79 | 79 | The [concepts.wiki#workflow | autosync] mode of Fossil makes it easy |
| 80 | -for multiple developers to work on a single branch and maintain a | |
| 81 | -linear line of development on that branch without needless forking | |
| 80 | +for multiple developers to work on a single branch and maintain | |
| 81 | +linear development on that branch and avoid needless forking | |
| 82 | 82 | and merging. |
| 83 | 83 | |
| 84 | 84 | <h3>3.3 Community</h3> |
| 85 | 85 | |
| 86 | 86 | Git has a huge user community. If following the herd and being |
| @@ -112,16 +112,16 @@ | ||
| 112 | 112 | |
| 113 | 113 | <h3>3.4 Complexity</h3> |
| 114 | 114 | |
| 115 | 115 | Git is a complex system. It can be tricky to use and requires a fair |
| 116 | 116 | amount of knowledge and experience to master. Fossil strives to be |
| 117 | -a much simpler system that can be learned and master much more quickly. | |
| 117 | +a much simpler system that can be learned and mastered much more quickly. | |
| 118 | 118 | Fossil strives to have fewer "gotchas" and quirks that can trip up a |
| 119 | 119 | developer. |
| 120 | 120 | |
| 121 | 121 | The ideal VCS should just get out of the way of the developer and allow |
| 122 | -the developer to focus 100% of their thinking to the project under | |
| 122 | +the developer to focus 100% of their thinking on the project under | |
| 123 | 123 | development. One should not have to stop and think about how to operate |
| 124 | 124 | the VCS. Of course, no VCS is ideal. Every VCS requires the developer |
| 125 | 125 | to think about version control to some extent. But one wants to minimize |
| 126 | 126 | the thinking about version control. |
| 127 | 127 | |
| 128 | 128 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -72,15 +72,15 @@ | |
| 72 | at a time. Git encourages a programming model where each developer |
| 73 | works in his or her own branch and then merges changes up the hierarchy |
| 74 | until they reach the master branch. |
| 75 | |
| 76 | Fossil is designed for smaller and non-hierarchical teams where all |
| 77 | developers are operating directly on the master branch, or at most one |
| 78 | a small number of well defined branches. |
| 79 | The [concepts.wiki#workflow | autosync] mode of Fossil makes it easy |
| 80 | for multiple developers to work on a single branch and maintain a |
| 81 | linear line of development on that branch without needless forking |
| 82 | and merging. |
| 83 | |
| 84 | <h3>3.3 Community</h3> |
| 85 | |
| 86 | Git has a huge user community. If following the herd and being |
| @@ -112,16 +112,16 @@ | |
| 112 | |
| 113 | <h3>3.4 Complexity</h3> |
| 114 | |
| 115 | Git is a complex system. It can be tricky to use and requires a fair |
| 116 | amount of knowledge and experience to master. Fossil strives to be |
| 117 | a much simpler system that can be learned and master much more quickly. |
| 118 | Fossil strives to have fewer "gotchas" and quirks that can trip up a |
| 119 | developer. |
| 120 | |
| 121 | The ideal VCS should just get out of the way of the developer and allow |
| 122 | the developer to focus 100% of their thinking to the project under |
| 123 | development. One should not have to stop and think about how to operate |
| 124 | the VCS. Of course, no VCS is ideal. Every VCS requires the developer |
| 125 | to think about version control to some extent. But one wants to minimize |
| 126 | the thinking about version control. |
| 127 | |
| 128 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -72,15 +72,15 @@ | |
| 72 | at a time. Git encourages a programming model where each developer |
| 73 | works in his or her own branch and then merges changes up the hierarchy |
| 74 | until they reach the master branch. |
| 75 | |
| 76 | Fossil is designed for smaller and non-hierarchical teams where all |
| 77 | developers are operating directly on the master branch, or at most |
| 78 | a small number of well defined branches. |
| 79 | The [concepts.wiki#workflow | autosync] mode of Fossil makes it easy |
| 80 | for multiple developers to work on a single branch and maintain |
| 81 | linear development on that branch and avoid needless forking |
| 82 | and merging. |
| 83 | |
| 84 | <h3>3.3 Community</h3> |
| 85 | |
| 86 | Git has a huge user community. If following the herd and being |
| @@ -112,16 +112,16 @@ | |
| 112 | |
| 113 | <h3>3.4 Complexity</h3> |
| 114 | |
| 115 | Git is a complex system. It can be tricky to use and requires a fair |
| 116 | amount of knowledge and experience to master. Fossil strives to be |
| 117 | a much simpler system that can be learned and mastered much more quickly. |
| 118 | Fossil strives to have fewer "gotchas" and quirks that can trip up a |
| 119 | developer. |
| 120 | |
| 121 | The ideal VCS should just get out of the way of the developer and allow |
| 122 | the developer to focus 100% of their thinking on the project under |
| 123 | development. One should not have to stop and think about how to operate |
| 124 | the VCS. Of course, no VCS is ideal. Every VCS requires the developer |
| 125 | to think about version control to some extent. But one wants to minimize |
| 126 | the thinking about version control. |
| 127 | |
| 128 |