diff options
author | 2017-03-03 13:40:06 +0000 | |
---|---|---|
committer | 2017-03-03 13:40:06 +0000 | |
commit | 5ed7cb33d54075cde7628c104d2ba6e4f2e4414d (patch) | |
tree | f1c865c1b2f7bde742e5a4f88b96bda04b0ae761 | |
parent | 16da107ff592c933b3c12236664eaf83b3b8435d (diff) |
Added a comment: Does this not work counter to locking / unlocking files?
-rw-r--r-- | doc/todo/utilising_the_mklink_command_on_windows_to_utilise_symlinks_and_therefore_indirect_mode_on_windows/comment_2_575d96ffa2a8f2cb1ba3d0e5c4ba4e6f._comment | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/todo/utilising_the_mklink_command_on_windows_to_utilise_symlinks_and_therefore_indirect_mode_on_windows/comment_2_575d96ffa2a8f2cb1ba3d0e5c4ba4e6f._comment b/doc/todo/utilising_the_mklink_command_on_windows_to_utilise_symlinks_and_therefore_indirect_mode_on_windows/comment_2_575d96ffa2a8f2cb1ba3d0e5c4ba4e6f._comment new file mode 100644 index 000000000..ad37ac8b0 --- /dev/null +++ b/doc/todo/utilising_the_mklink_command_on_windows_to_utilise_symlinks_and_therefore_indirect_mode_on_windows/comment_2_575d96ffa2a8f2cb1ba3d0e5c4ba4e6f._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="jason.dixon.email@aa0e536a2ec2877d6f666108dbbc6e39bbe87ac0" + nickname="jason.dixon.email" + avatar="http://cdn.libravatar.org/avatar/fbe9050fc83bbd536d307d87ea14d4bc" + subject="Does this not work counter to locking / unlocking files?" + date="2017-03-03T13:40:06Z" + content=""" +Perhaps I understand this wrong. But if you're in a position to be viewing symlinks, then the file is in effect, locked right? So in the situation that a windows user is trying to edit a file that is currently symlinked, they shouldn't be allowed to save at all. They should have unlocked the file first, thus replacing the link with the actual file. A simple fix would be to have the symlink read-only just as the file tucked away in .git/annex/objects is. + +As I said, I'm probably looking at this in entirely the wrong way. +"""]] |