Fossil SCM
Fixed several "descendents" typos. (It's "descendants".) There's still one remaining in sqlite3.c, but of course fixing that here won't help.
Commit
85f119dc7d3c732217b3cee19bed876df552ea54e6abe651cb99a526dddfbfc3
Parent
c2f0063f1e4fe86…
2 files changed
+1
-1
+2
-2
+1
-1
| --- src/finfo.c | ||
| +++ src/finfo.c | ||
| @@ -319,11 +319,11 @@ | ||
| 319 | 319 | ** m=HASH Mark this particular file version. |
| 320 | 320 | ** n=NUM Show the first NUM changes only |
| 321 | 321 | ** name=FILENAME (Required) name of file whose history to show |
| 322 | 322 | ** brbg Background color by branch name |
| 323 | 323 | ** ubg Background color by user name |
| 324 | -** from=HASH Ancestors only (not descendents) of the version of | |
| 324 | +** from=HASH Ancestors only (not descendants) of the version of | |
| 325 | 325 | ** the file in this particular check-in. |
| 326 | 326 | ** to=HASH If both from= and to= are supplied, only show those |
| 327 | 327 | ** changes on the direct path between the two given |
| 328 | 328 | ** checkins. |
| 329 | 329 | ** showid Show RID values for debugging |
| 330 | 330 |
| --- src/finfo.c | |
| +++ src/finfo.c | |
| @@ -319,11 +319,11 @@ | |
| 319 | ** m=HASH Mark this particular file version. |
| 320 | ** n=NUM Show the first NUM changes only |
| 321 | ** name=FILENAME (Required) name of file whose history to show |
| 322 | ** brbg Background color by branch name |
| 323 | ** ubg Background color by user name |
| 324 | ** from=HASH Ancestors only (not descendents) of the version of |
| 325 | ** the file in this particular check-in. |
| 326 | ** to=HASH If both from= and to= are supplied, only show those |
| 327 | ** changes on the direct path between the two given |
| 328 | ** checkins. |
| 329 | ** showid Show RID values for debugging |
| 330 |
| --- src/finfo.c | |
| +++ src/finfo.c | |
| @@ -319,11 +319,11 @@ | |
| 319 | ** m=HASH Mark this particular file version. |
| 320 | ** n=NUM Show the first NUM changes only |
| 321 | ** name=FILENAME (Required) name of file whose history to show |
| 322 | ** brbg Background color by branch name |
| 323 | ** ubg Background color by user name |
| 324 | ** from=HASH Ancestors only (not descendants) of the version of |
| 325 | ** the file in this particular check-in. |
| 326 | ** to=HASH If both from= and to= are supplied, only show those |
| 327 | ** changes on the direct path between the two given |
| 328 | ** checkins. |
| 329 | ** showid Show RID values for debugging |
| 330 |
+2
-2
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -248,19 +248,19 @@ | ||
| 248 | 248 | database file which provides ACID transactions and a high-level query |
| 249 | 249 | language. |
| 250 | 250 | This difference is more than an implementation detail. It has important |
| 251 | 251 | practical consequences. |
| 252 | 252 | |
| 253 | -One notable consequence is that it is difficult to find the descendents | |
| 253 | +One notable consequence is that it is difficult to find the descendants | |
| 254 | 254 | of check-ins in Git. |
| 255 | 255 | One can easily locate the ancestors of a particular Git check-in |
| 256 | 256 | by following the pointers embedded in the check-in object, but it is |
| 257 | 257 | difficult to go the other direction and locate the descendants of a |
| 258 | 258 | check-in. It is so difficult, in fact, that neither native Git nor |
| 259 | 259 | GitHub provide this capability short of crawling the |
| 260 | 260 | [https://www.git-scm.com/docs/git-log|commit log]. With Fossil, |
| 261 | -on the other hand, finding descendents is a simple SQL query. | |
| 261 | +on the other hand, finding descendants is a simple SQL query. | |
| 262 | 262 | It is common in Fossil to ask to see |
| 263 | 263 | [/timeline?df=release&y=ci|all check-ins since the last release]. |
| 264 | 264 | Git lets you see "what came before". Fossil makes it just as |
| 265 | 265 | easy to also see "what came after". |
| 266 | 266 | |
| 267 | 267 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -248,19 +248,19 @@ | |
| 248 | database file which provides ACID transactions and a high-level query |
| 249 | language. |
| 250 | This difference is more than an implementation detail. It has important |
| 251 | practical consequences. |
| 252 | |
| 253 | One notable consequence is that it is difficult to find the descendents |
| 254 | of check-ins in Git. |
| 255 | One can easily locate the ancestors of a particular Git check-in |
| 256 | by following the pointers embedded in the check-in object, but it is |
| 257 | difficult to go the other direction and locate the descendants of a |
| 258 | check-in. It is so difficult, in fact, that neither native Git nor |
| 259 | GitHub provide this capability short of crawling the |
| 260 | [https://www.git-scm.com/docs/git-log|commit log]. With Fossil, |
| 261 | on the other hand, finding descendents is a simple SQL query. |
| 262 | It is common in Fossil to ask to see |
| 263 | [/timeline?df=release&y=ci|all check-ins since the last release]. |
| 264 | Git lets you see "what came before". Fossil makes it just as |
| 265 | easy to also see "what came after". |
| 266 | |
| 267 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -248,19 +248,19 @@ | |
| 248 | database file which provides ACID transactions and a high-level query |
| 249 | language. |
| 250 | This difference is more than an implementation detail. It has important |
| 251 | practical consequences. |
| 252 | |
| 253 | One notable consequence is that it is difficult to find the descendants |
| 254 | of check-ins in Git. |
| 255 | One can easily locate the ancestors of a particular Git check-in |
| 256 | by following the pointers embedded in the check-in object, but it is |
| 257 | difficult to go the other direction and locate the descendants of a |
| 258 | check-in. It is so difficult, in fact, that neither native Git nor |
| 259 | GitHub provide this capability short of crawling the |
| 260 | [https://www.git-scm.com/docs/git-log|commit log]. With Fossil, |
| 261 | on the other hand, finding descendants is a simple SQL query. |
| 262 | It is common in Fossil to ask to see |
| 263 | [/timeline?df=release&y=ci|all check-ins since the last release]. |
| 264 | Git lets you see "what came before". Fossil makes it just as |
| 265 | easy to also see "what came after". |
| 266 | |
| 267 |