diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2014-01-06 15:48:36 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-01-06 15:48:36 +0000 |
| commit | 2e287941722041bf75506a3e3151e83b1ac4eb41 (patch) | |
| tree | 72a615050e617eaf4f9d94eb99cc8069ee609d4d | |
| parent | e999b351a2c7b3d389293dc5dd2aa27679470311 (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/git_annex_on_osx_only_creating_symlinks__63____63__/comment_4_99286f17a87049c303f2aa34c0a90286._comment | 13 |
1 files changed, 13 insertions, 0 deletions
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. +"""]] |