Skip to content
Snippets Groups Projects
Commit 27a53cf99d2c authored by Arseniy Alekseyev's avatar Arseniy Alekseyev
Browse files

doc: clarify the purpose and meaning of MTIME_SECOND_AMBIGUOUS

I found the existing description pretty hard to understand.
Hopefully this phrasing makes things clearer.
parent 59c293612689
No related branches found
No related tags found
1 merge request!1104Draft: doc: clarify the purpose and meaning of MTIME_SECOND_AMBIGUOUS
......@@ -616,4 +616,5 @@
extracted from the file system. If unset it should be considered a normal
file instead.
`MTIME_SECOND_AMBIGUOUS`
......@@ -619,6 +620,7 @@
`MTIME_SECOND_AMBIGUOUS`
This flag is relevant only when `HAS_FILE_MTIME` is set. When set, the
`mtime` stored in the entry is only valid for comparison with timestamps
that have nanosecond information. If available timestamp does not carries
nanosecond information, the `mtime` should be ignored and no optimization
can be applied.
This flag is relevant only when `HAS_FILE_MTIME` is set. If not set, the
`mtime` stored in the entry is usable even without the nanosecond
information. If set, the nanosecond information is required
to decide whether or not the file was modified, so this timestamp
can't be safely used with 1s time resolution, in particular
when interacting with dirstate-v1.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment