Fossil SCM
More grammar fixes
Commit
9f135f2f4c753f9775cadabec55869b1a47709dfde2b7e95834e8cd3d3504569
Parent
f36fb951ee89184…
1 file changed
+4
-4
+4
-4
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -287,16 +287,16 @@ | ||
| 287 | 287 | walk the data and compute the result. And since that is a lot more |
| 288 | 288 | work, the question is seldom asked. |
| 289 | 289 | |
| 290 | 290 | The ease of querying Fossil data using SQL means that status or |
| 291 | 291 | history information about the project under management is easier |
| 292 | -to obtain. And being easier means that it is more likely to happen. | |
| 292 | +to obtain. Being easier means that it is more likely to happen. | |
| 293 | 293 | Fossil reports tend to be more detailed and useful. |
| 294 | 294 | Consider the [/timeline?c=6df7a853ec16865b|this Fossil timeline] |
| 295 | -compared to its | |
| 296 | -[https://github.com/drhsqlite/fossil-mirror/commits/master?after=f720c106d297ca1f61bccb30c5c191b88a626d01+34|its | |
| 297 | -closest equivalent in GitHub]. Judge for yourself: Which of those | |
| 295 | +compared to | |
| 296 | +[https://github.com/drhsqlite/fossil-mirror/commits/master?after=f720c106d297ca1f61bccb30c5c191b88a626d01+34 | | |
| 297 | +its closest equivalent in GitHub]. Judge for yourself: Which of those | |
| 298 | 298 | reports is more useful to a developer trying to understand what happened? |
| 299 | 299 | |
| 300 | 300 | The bottom line is that even though Fossil and Git are built around |
| 301 | 301 | the same low-level data structure, the use of SQL |
| 302 | 302 | to query this data makes the data more accessible in Fossil, resulting |
| 303 | 303 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -287,16 +287,16 @@ | |
| 287 | walk the data and compute the result. And since that is a lot more |
| 288 | work, the question is seldom asked. |
| 289 | |
| 290 | The ease of querying Fossil data using SQL means that status or |
| 291 | history information about the project under management is easier |
| 292 | to obtain. And being easier means that it is more likely to happen. |
| 293 | Fossil reports tend to be more detailed and useful. |
| 294 | Consider the [/timeline?c=6df7a853ec16865b|this Fossil timeline] |
| 295 | compared to its |
| 296 | [https://github.com/drhsqlite/fossil-mirror/commits/master?after=f720c106d297ca1f61bccb30c5c191b88a626d01+34|its |
| 297 | closest equivalent in GitHub]. Judge for yourself: Which of those |
| 298 | reports is more useful to a developer trying to understand what happened? |
| 299 | |
| 300 | The bottom line is that even though Fossil and Git are built around |
| 301 | the same low-level data structure, the use of SQL |
| 302 | to query this data makes the data more accessible in Fossil, resulting |
| 303 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -287,16 +287,16 @@ | |
| 287 | walk the data and compute the result. And since that is a lot more |
| 288 | work, the question is seldom asked. |
| 289 | |
| 290 | The ease of querying Fossil data using SQL means that status or |
| 291 | history information about the project under management is easier |
| 292 | to obtain. Being easier means that it is more likely to happen. |
| 293 | Fossil reports tend to be more detailed and useful. |
| 294 | Consider the [/timeline?c=6df7a853ec16865b|this Fossil timeline] |
| 295 | compared to |
| 296 | [https://github.com/drhsqlite/fossil-mirror/commits/master?after=f720c106d297ca1f61bccb30c5c191b88a626d01+34 | |
| 297 | its closest equivalent in GitHub]. Judge for yourself: Which of those |
| 298 | reports is more useful to a developer trying to understand what happened? |
| 299 | |
| 300 | The bottom line is that even though Fossil and Git are built around |
| 301 | the same low-level data structure, the use of SQL |
| 302 | to query this data makes the data more accessible in Fossil, resulting |
| 303 |