From 1ca8cdebafbc9cb9fee4cd16316492fa3c273dbd Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlzlNQbf6wBgv9j6-UqfpXcQyAYMF8S3t4" Date: Sat, 3 Aug 2013 11:47:58 +0000 Subject: --- .../Is_it_possible_to_make_git-sync_not_nullify_symlinks__63__.mdwn | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/forum/Is_it_possible_to_make_git-sync_not_nullify_symlinks__63__.mdwn b/doc/forum/Is_it_possible_to_make_git-sync_not_nullify_symlinks__63__.mdwn index 7101128f9..9c41acb70 100644 --- a/doc/forum/Is_it_possible_to_make_git-sync_not_nullify_symlinks__63__.mdwn +++ b/doc/forum/Is_it_possible_to_make_git-sync_not_nullify_symlinks__63__.mdwn @@ -7,8 +7,11 @@ There's one small problem. Say: 1) I've already published a file using `git annex get file-to-update` + 2) I update that file on my computer + 3) I do `git annex sync` + 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. -- cgit v1.2.3