Fossil SCM
Fixed some grammar errors in fossil-v-git's new "Accepting Contributions" material.
Commit
34d758bf86b6aba6e496254fe5b3b4c6995c8030b4c10ad73c4674334cbb9b8d
Parent
d1c61803fc08e25…
1 file changed
+2
-2
+2
-2
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -321,12 +321,12 @@ | ||
| 321 | 321 | things, but only by studying their art deeply for years. This does not |
| 322 | 322 | strike us as a good use of the user's time. We believe it's better to |
| 323 | 323 | have a simpler tool with a more easily internalized behavior set, which |
| 324 | 324 | you can use quickly then set aside in order to get back to your main |
| 325 | 325 | task of producing the content that you manage in the DVCS. We achieve |
| 326 | -that by carefully choosing which users to give commit bits to, and which | |
| 327 | -of their feature branches get merged down to trunk. | |
| 326 | +that by carefully choosing which users to give commit bits to, then which | |
| 327 | +of their feature branches to merge down to trunk. | |
| 328 | 328 | |
| 329 | 329 | |
| 330 | 330 | <h3 id="branches">2.4 Individual Branches vs. The Entire Change History</h3> |
| 331 | 331 | |
| 332 | 332 | Both Fossil and Git store history as a directed acyclic graph (DAG) |
| 333 | 333 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -321,12 +321,12 @@ | |
| 321 | things, but only by studying their art deeply for years. This does not |
| 322 | strike us as a good use of the user's time. We believe it's better to |
| 323 | have a simpler tool with a more easily internalized behavior set, which |
| 324 | you can use quickly then set aside in order to get back to your main |
| 325 | task of producing the content that you manage in the DVCS. We achieve |
| 326 | that by carefully choosing which users to give commit bits to, and which |
| 327 | of their feature branches get merged down to trunk. |
| 328 | |
| 329 | |
| 330 | <h3 id="branches">2.4 Individual Branches vs. The Entire Change History</h3> |
| 331 | |
| 332 | Both Fossil and Git store history as a directed acyclic graph (DAG) |
| 333 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -321,12 +321,12 @@ | |
| 321 | things, but only by studying their art deeply for years. This does not |
| 322 | strike us as a good use of the user's time. We believe it's better to |
| 323 | have a simpler tool with a more easily internalized behavior set, which |
| 324 | you can use quickly then set aside in order to get back to your main |
| 325 | task of producing the content that you manage in the DVCS. We achieve |
| 326 | that by carefully choosing which users to give commit bits to, then which |
| 327 | of their feature branches to merge down to trunk. |
| 328 | |
| 329 | |
| 330 | <h3 id="branches">2.4 Individual Branches vs. The Entire Change History</h3> |
| 331 | |
| 332 | Both Fossil and Git store history as a directed acyclic graph (DAG) |
| 333 |