From 2e287941722041bf75506a3e3151e83b1ac4eb41 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Mon, 6 Jan 2014 15:48:36 +0000 Subject: Added a comment --- .../comment_4_99286f17a87049c303f2aa34c0a90286._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/forum/git_annex_on_osx_only_creating_symlinks__63____63__/comment_4_99286f17a87049c303f2aa34c0a90286._comment diff --git a/doc/forum/git_annex_on_osx_only_creating_symlinks__63____63__/comment_4_99286f17a87049c303f2aa34c0a90286._comment b/doc/forum/git_annex_on_osx_only_creating_symlinks__63____63__/comment_4_99286f17a87049c303f2aa34c0a90286._comment new file mode 100644 index 000000000..d21d87145 --- /dev/null +++ b/doc/forum/git_annex_on_osx_only_creating_symlinks__63____63__/comment_4_99286f17a87049c303f2aa34c0a90286._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.35" + subject="comment 4" + date="2014-01-06T15:48:36Z" + content=""" +@Tim, you do not seem to be having the problem that the OP described. + +It is completely normal for git-annex to represent a file whose content is not present in the repository as a broken symlink. +Typically, git-annex preserves at least one copy of the file in one of your repositories. But if you `git annex add $file; git annex drop --force $file`, you will be left in exactly the situation you describe. + +You can use `git annex log $file` to see a log of which repositories contained a copy of the file in the past, and see what times the file was removed from each repository. This might give clues to what operation caused the last copy of the file to be lose. +"""]] -- cgit v1.2.3