Fossil SCM
Using the less jargony term "crawling" instead of "grovel" in the Fossil v Git article.
Commit
3f6f7deaf6d434d33d3ce75e704630a30011c9702b2643e587752d90f522791a
Parent
e673065280bbd81…
1 file changed
+1
-2
+1
-2
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -253,12 +253,11 @@ | ||
| 253 | 253 | |
| 254 | 254 | With Git, one can easily locate the ancestors of a particular check-in |
| 255 | 255 | by following the pointers embedded in the check-in object, but it is |
| 256 | 256 | difficult to go the other direction and locate the descendants of a |
| 257 | 257 | check-in. It is so difficult, in fact, that neither native Git nor |
| 258 | -GitHub provide this capability short of | |
| 259 | -[http://catb.org/jargon/html/G/grovel.html|groveling] the | |
| 258 | +GitHub provide this capability short of crawling the | |
| 260 | 259 | [https://www.git-scm.com/docs/git-log|commit log]. With Git, if you |
| 261 | 260 | are looking at some historical check-in then you cannot ask "What came |
| 262 | 261 | next?" or "What are the children of this check-in?" |
| 263 | 262 | |
| 264 | 263 | Fossil, on the other hand, parses essential information about check-ins |
| 265 | 264 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -253,12 +253,11 @@ | |
| 253 | |
| 254 | With Git, one can easily locate the ancestors of a particular check-in |
| 255 | by following the pointers embedded in the check-in object, but it is |
| 256 | difficult to go the other direction and locate the descendants of a |
| 257 | check-in. It is so difficult, in fact, that neither native Git nor |
| 258 | GitHub provide this capability short of |
| 259 | [http://catb.org/jargon/html/G/grovel.html|groveling] the |
| 260 | [https://www.git-scm.com/docs/git-log|commit log]. With Git, if you |
| 261 | are looking at some historical check-in then you cannot ask "What came |
| 262 | next?" or "What are the children of this check-in?" |
| 263 | |
| 264 | Fossil, on the other hand, parses essential information about check-ins |
| 265 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -253,12 +253,11 @@ | |
| 253 | |
| 254 | With Git, one can easily locate the ancestors of a particular check-in |
| 255 | by following the pointers embedded in the check-in object, but it is |
| 256 | difficult to go the other direction and locate the descendants of a |
| 257 | check-in. It is so difficult, in fact, that neither native Git nor |
| 258 | GitHub provide this capability short of crawling the |
| 259 | [https://www.git-scm.com/docs/git-log|commit log]. With Git, if you |
| 260 | are looking at some historical check-in then you cannot ask "What came |
| 261 | next?" or "What are the children of this check-in?" |
| 262 | |
| 263 | Fossil, on the other hand, parses essential information about check-ins |
| 264 |