This makes the dirstate-v2 file format match dirstate-v1 for the order of
mode, size, and mtime. This order does not matter as long as these
components are handled through named fields/attributes in code, but in a few
places we still have tuples so having the same order everywhere might help
avoid a bug that might not be obvious since those components have the same type.
Details
Details
- Reviewers
- None
- Group Reviewers
hg-reviewers - Commits
- rHG6e01bcd111d2: dirstate-v2: Swap the order of size and mtime on disk
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Branch
- default
- Lint
No Linters Available - Unit
No Unit Test Coverage
Event Timeline
Comment Actions
I’ve split this from D11547.
Because of how BytesCast is used, the struct definition defines the file format.
Comment Actions
This makes the dirstate-v2 file format match dirstate-v2 for the order of
Should the second "v2" be "v1?
(And I assume "Change swap" can be just "Swap".)