summaryrefslogtreecommitdiff
path: root/doc/direct_mode/comment_14_03a02e689d92faa596de98e02b2ffe28._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/direct_mode/comment_14_03a02e689d92faa596de98e02b2ffe28._comment')
-rw-r--r--doc/direct_mode/comment_14_03a02e689d92faa596de98e02b2ffe28._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/direct_mode/comment_14_03a02e689d92faa596de98e02b2ffe28._comment b/doc/direct_mode/comment_14_03a02e689d92faa596de98e02b2ffe28._comment
new file mode 100644
index 000000000..ce47a5eb8
--- /dev/null
+++ b/doc/direct_mode/comment_14_03a02e689d92faa596de98e02b2ffe28._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.2"
+ subject="comment 14"
+ date="2014-07-16T17:51:28Z"
+ content="""
+I kinda wish people would post questions to the forum, and not clutter up this page..
+
+Anyway, there have been past bugs in the direct mode code that caused some files to not be checked out in direct mode, but stay as symlinks pointing at the content. That can be fixed by running `git annex fsck`. But, I am not aware of any problem that can leave a git-annex symlink that is not checked into git at all. Perhaps you copied the symlink from another location?
+"""]]