diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawlzlNQbf6wBgv9j6-UqfpXcQyAYMF8S3t4 <Tim@web> | 2013-08-03 11:47:58 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-08-03 11:47:58 +0000 |
| commit | 1ca8cdebafbc9cb9fee4cd16316492fa3c273dbd (patch) | |
| tree | 6df7ad3c2dd1b1c070b701d5fb8497b4e3e276ca | |
| parent | 5636d32e28f7f8729d23d48332a67f7a73b40b12 (diff) | |
| -rw-r--r-- | doc/forum/Is_it_possible_to_make_git-sync_not_nullify_symlinks__63__.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
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. |