mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment: Does this not work counter to locking / unlocking files?

Browse source
This commit is contained in:
jason.dixon.email@aa0e536a2ec2877d6f666108dbbc6e39bbe87ac0 2017-03-03 13:40:06 +00:00 • committed by admin
parent afc65319af
commit 86508537c5
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/todo/utilising_the_mklink_command_on_windows_to_utilise_symlinks_and_therefore_indirect_mode_on_windows/comment_2_575d96ffa2a8f2cb1ba3d0e5c4ba4e6f._comment Normal file
View file

@ -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.
"""]]