diff options
-rw-r--r-- | doc/forum/some_symlinks_left_in_direct_mode/comment_1_fd8d8107861453f0aa6b2c390e369307._comment | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/forum/some_symlinks_left_in_direct_mode/comment_1_fd8d8107861453f0aa6b2c390e369307._comment b/doc/forum/some_symlinks_left_in_direct_mode/comment_1_fd8d8107861453f0aa6b2c390e369307._comment new file mode 100644 index 000000000..29e8b7490 --- /dev/null +++ b/doc/forum/some_symlinks_left_in_direct_mode/comment_1_fd8d8107861453f0aa6b2c390e369307._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2014-12-02T18:53:32Z" + content=""" +Well, it's normal to have broken symlinks if the content of a file +is not present. `git annex get` will get the file content +and replace the symlink with it. + +If the symlink is not broken, you can run `git annex fsck` on the file +and it will notice and fix this inconsistency. + +Some old versions of git-annex had bugs in direct mode that could result +in files being left as symlinks like that. I have not seen any bugs +lately in that area. If you have a way to get a repository into that +state, file a bug report with a test case. +"""]] |