Fossil SCM
Fix one error and add an additional note to the article on the annotate algorithm.
Commit
9828493c998b9651e7d569e24665eadc89d63ee5
Parent
91af24e6c942da9…
1 file changed
+6
-2
+6
-2
| --- www/blame.wiki | ||
| +++ www/blame.wiki | ||
| @@ -50,9 +50,13 @@ | ||
| 50 | 50 | [/help?cmd=/annotate|/annotate] webpage only shows those lines that where |
| 51 | 51 | changed by the 20 most recent modifications to the file. This allows |
| 52 | 52 | the loop on step 6 to terminate after only 19 diffs instead of the hundreds |
| 53 | 53 | or thousands of diffs that might be required for a frequently modified file. |
| 54 | 54 | |
| 55 | -As currently implemented (2015-12-12) the annotate algorithm does not | |
| 55 | +As currently implemented (as of 2015-12-12) the annotate algorithm does not | |
| 56 | 56 | follow files across name changes. File name change information is |
| 57 | 57 | available in the database, and so the algorithm could be enhanced to follow |
| 58 | -files across name changes by modifications to step 2. | |
| 58 | +files across name changes by modifications to step 3. | |
| 59 | + | |
| 60 | +Step 2 is interesting in that it is | |
| 61 | +[/artifact/6cb824a0417?ln=196-201 | implemented] using a | |
| 62 | +[https://www.sqlite.org/lang_with.html#recursivecte|recursive common table expression]. | |
| 59 | 63 |
| --- www/blame.wiki | |
| +++ www/blame.wiki | |
| @@ -50,9 +50,13 @@ | |
| 50 | [/help?cmd=/annotate|/annotate] webpage only shows those lines that where |
| 51 | changed by the 20 most recent modifications to the file. This allows |
| 52 | the loop on step 6 to terminate after only 19 diffs instead of the hundreds |
| 53 | or thousands of diffs that might be required for a frequently modified file. |
| 54 | |
| 55 | As currently implemented (2015-12-12) the annotate algorithm does not |
| 56 | follow files across name changes. File name change information is |
| 57 | available in the database, and so the algorithm could be enhanced to follow |
| 58 | files across name changes by modifications to step 2. |
| 59 |
| --- www/blame.wiki | |
| +++ www/blame.wiki | |
| @@ -50,9 +50,13 @@ | |
| 50 | [/help?cmd=/annotate|/annotate] webpage only shows those lines that where |
| 51 | changed by the 20 most recent modifications to the file. This allows |
| 52 | the loop on step 6 to terminate after only 19 diffs instead of the hundreds |
| 53 | or thousands of diffs that might be required for a frequently modified file. |
| 54 | |
| 55 | As currently implemented (as of 2015-12-12) the annotate algorithm does not |
| 56 | follow files across name changes. File name change information is |
| 57 | available in the database, and so the algorithm could be enhanced to follow |
| 58 | files across name changes by modifications to step 3. |
| 59 | |
| 60 | Step 2 is interesting in that it is |
| 61 | [/artifact/6cb824a0417?ln=196-201 | implemented] using a |
| 62 | [https://www.sqlite.org/lang_with.html#recursivecte|recursive common table expression]. |
| 63 |