From 86508537c5cb33fc7b570c26c09cc510fe76c18c Mon Sep 17 00:00:00 2001 From: "jason.dixon.email@aa0e536a2ec2877d6f666108dbbc6e39bbe87ac0" Date: Fri, 3 Mar 2017 13:40:06 +0000 Subject: [PATCH] Added a comment: Does this not work counter to locking / unlocking files? --- ...omment_2_575d96ffa2a8f2cb1ba3d0e5c4ba4e6f._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/todo/utilising_the_mklink_command_on_windows_to_utilise_symlinks_and_therefore_indirect_mode_on_windows/comment_2_575d96ffa2a8f2cb1ba3d0e5c4ba4e6f._comment 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 0000000000..ad37ac8b05 --- /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. +"""]]