Fossil SCM
Correct a small bit of internal-doc misinformation reported in [forum:9ed20acf6a|forum post 9ed20acf6a].
Commit
dd67906cbd9ebad731b2038959e378d7b5226ebbda9aa837b762c384444db40d
Parent
a24a790f3d6c0f7…
1 file changed
+4
-4
+4
-4
| --- src/vfile.c | ||
| +++ src/vfile.c | ||
| @@ -159,14 +159,14 @@ | ||
| 159 | 159 | ** |
| 160 | 160 | ** If the size of the file has changed, then we always know that the file |
| 161 | 161 | ** changed without having to look at the mtime or on-disk content. |
| 162 | 162 | ** |
| 163 | 163 | ** The mtime of the file is only a factor if the mtime-changes setting |
| 164 | -** is false and the CKSIG_HASH flag is false. If the mtime-changes | |
| 165 | -** setting is true (or undefined - it defaults to true) or if CKSIG_HASH | |
| 166 | -** is true, then we do not trust the mtime and will examine the on-disk | |
| 167 | -** content to determine if a file really is the same. | |
| 164 | +** is true (or undefined - it defaults to true) and the CKSIG_HASH | |
| 165 | +** flag is false. If the mtime-changes setting is false or if | |
| 166 | +** CKSIG_HASH is true, then we do not trust the mtime and will examine | |
| 167 | +** the on-disk content to determine if a file really is the same. | |
| 168 | 168 | ** |
| 169 | 169 | ** If the mtime is used, it is used only to determine if files are the same. |
| 170 | 170 | ** If the mtime of a file has changed, we still examine the on-disk content |
| 171 | 171 | ** to see whether or not the edit was a null-edit. |
| 172 | 172 | */ |
| 173 | 173 |
| --- src/vfile.c | |
| +++ src/vfile.c | |
| @@ -159,14 +159,14 @@ | |
| 159 | ** |
| 160 | ** If the size of the file has changed, then we always know that the file |
| 161 | ** changed without having to look at the mtime or on-disk content. |
| 162 | ** |
| 163 | ** The mtime of the file is only a factor if the mtime-changes setting |
| 164 | ** is false and the CKSIG_HASH flag is false. If the mtime-changes |
| 165 | ** setting is true (or undefined - it defaults to true) or if CKSIG_HASH |
| 166 | ** is true, then we do not trust the mtime and will examine the on-disk |
| 167 | ** content to determine if a file really is the same. |
| 168 | ** |
| 169 | ** If the mtime is used, it is used only to determine if files are the same. |
| 170 | ** If the mtime of a file has changed, we still examine the on-disk content |
| 171 | ** to see whether or not the edit was a null-edit. |
| 172 | */ |
| 173 |
| --- src/vfile.c | |
| +++ src/vfile.c | |
| @@ -159,14 +159,14 @@ | |
| 159 | ** |
| 160 | ** If the size of the file has changed, then we always know that the file |
| 161 | ** changed without having to look at the mtime or on-disk content. |
| 162 | ** |
| 163 | ** The mtime of the file is only a factor if the mtime-changes setting |
| 164 | ** is true (or undefined - it defaults to true) and the CKSIG_HASH |
| 165 | ** flag is false. If the mtime-changes setting is false or if |
| 166 | ** CKSIG_HASH is true, then we do not trust the mtime and will examine |
| 167 | ** the on-disk content to determine if a file really is the same. |
| 168 | ** |
| 169 | ** If the mtime is used, it is used only to determine if files are the same. |
| 170 | ** If the mtime of a file has changed, we still examine the on-disk content |
| 171 | ** to see whether or not the edit was a null-edit. |
| 172 | */ |
| 173 |