Changeset View
Changeset View
Standalone View
Standalone View
mercurial/helptext/internals/dirstate-v2.txt
Show First 20 Lines • Show All 384 Lines • ▼ Show 20 Line(s) | Starting from least-significant, bit masks are:: | ||||
MODE_IS_SYMLINK = 1 << 7 | MODE_IS_SYMLINK = 1 << 7 | ||||
EXPECTED_STATE_IS_MODIFIED = 1 << 8 | EXPECTED_STATE_IS_MODIFIED = 1 << 8 | ||||
ALL_UNKNOWN_RECORDED = 1 << 9 | ALL_UNKNOWN_RECORDED = 1 << 9 | ||||
ALL_IGNORED_RECORDED = 1 << 10 | ALL_IGNORED_RECORDED = 1 << 10 | ||||
HAS_FALLBACK_EXEC = 1 << 11 | HAS_FALLBACK_EXEC = 1 << 11 | ||||
FALLBACK_EXEC = 1 << 12 | FALLBACK_EXEC = 1 << 12 | ||||
HAS_FALLBACK_SYMLINK = 1 << 13 | HAS_FALLBACK_SYMLINK = 1 << 13 | ||||
FALLBACK_SYMLINK = 1 << 14 | FALLBACK_SYMLINK = 1 << 14 | ||||
MTIME_SECOND_AMBIGUOUS = 1 << 15 | |||||
The meaning of each bit is described below. | The meaning of each bit is described below. | ||||
Other bits are unset. | Other bits are unset. | ||||
They may be assigned meaning if the future, | They may be assigned meaning if the future, | ||||
with the limitation that Mercurial versions that pre-date such meaning | with the limitation that Mercurial versions that pre-date such meaning | ||||
will always reset those bits to unset when writing nodes. | will always reset those bits to unset when writing nodes. | ||||
(A new node is written for any mutation in its subtree, | (A new node is written for any mutation in its subtree, | ||||
▲ Show 20 Lines • Show All 186 Lines • ▼ Show 20 Line(s) | `HAS_FALLBACK_SYMLINK` | ||||
system or operating system does not support that property, (e.g. | system or operating system does not support that property, (e.g. | ||||
Windows). | Windows). | ||||
`FALLBACK_SYMLINK` | `FALLBACK_SYMLINK` | ||||
Should be ignored if `HAS_FALLBACK_SYMLINK` is unset. If set the file for | Should be ignored if `HAS_FALLBACK_SYMLINK` is unset. If set the file for | ||||
this entry should be considered a symlink if that information cannot be | this entry should be considered a symlink if that information cannot be | ||||
extracted from the file system. If unset it should be considered a normal | extracted from the file system. If unset it should be considered a normal | ||||
file instead. | file instead. | ||||
`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 optimisation | |||||
can be applied. |