p4vfs doesn't respect the servers +m flag
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 308
- Forks
- 20
- Avg merge
- 14h 56m
- Merged PRs (30d)
- 1
Description
p4vfs always uses the current time as timestamp when syncing files even if the server has +m modifier associated with the file.
This breaks all tooling relying on modtime.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the p4vfs file-sync path that assigns timestamps, then review how server file metadata and the +m modifier are represented. Reproduce a sync from a server file with +m and verify that the local modification time matches the server value rather than the current time; confirm tooling relying on modtime is no longer broken.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100