Replies: 1 comment
-
No, not entirely. It would be valid for your provider to create a hard link to c:\src\foo.c in its PRJ_GET_PLACEHOLDER_INFO_CB callback. But since there's no copy-on-write mechanism that would end up allowing the user to modify c:\src\foo.c if they had modify access to the file. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Suppose a mirror file system:
Is it possible to share the copies so if the file src\foo.c is not modified, the same file content is present in copy00 and copy01?
I mean, suppose foo.c is 10GB, what I want is to use just 10GB overall, not 10GB copied 3 times as the default behavior does.
(It would be some sort of copy on write).
Beta Was this translation helpful? Give feedback.
All reactions