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

Browse source
This commit is contained in:
https://www.google.com/accounts/o8/id?id=AItOawlzlNQbf6wBgv9j6-UqfpXcQyAYMF8S3t4 2013-08-03 11:47:58 +00:00 • committed by admin
parent 436c0afff6
commit 426e6741ea
1 changed files with 3 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

3
doc/forum/Is_it_possible_to_make_git-sync_not_nullify_symlinks__63__.mdwn
View file

@ -7,8 +7,11 @@ There's one small problem.
Say: Say:
1) I've already published a file using `git annex get file-to-update` 1) I've already published a file using `git annex get file-to-update`
2) I update that file on my computer 2) I update that file on my computer
3) I do `git annex sync` 3) I do `git annex sync`
4) I do `git annex get file-to-update` 4) I do `git annex get file-to-update`
Between steps 3 and 4, file-to-update goes from being an accessible web resource to being a dead symlink. It's not really a problem for me, as hardly anyone visits my site. But it would be nice if I could make `sync` leave the old symlink to the old file until I `get`ed the new one. Between steps 3 and 4, file-to-update goes from being an accessible web resource to being a dead symlink. It's not really a problem for me, as hardly anyone visits my site. But it would be nice if I could make `sync` leave the old symlink to the old file until I `get`ed the new one.