summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-10-31 14:46:40 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-10-31 14:46:40 -0400
commit1eb665d2178d18f9b1363ead21a592151d7f8f8a (patch)
tree72ac57f2b4eb5443b8531d279d4fe2a416da6ce1
parent1d6c743e4ccbc3e8abb5138335bc32ad51245942 (diff)
comment
-rw-r--r--doc/forum/Problems_with_FAT_links/comment_4_0a5f0239b3b6376672c8d91eaf68a460._comment20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/forum/Problems_with_FAT_links/comment_4_0a5f0239b3b6376672c8d91eaf68a460._comment b/doc/forum/Problems_with_FAT_links/comment_4_0a5f0239b3b6376672c8d91eaf68a460._comment
new file mode 100644
index 000000000..02cb830d3
--- /dev/null
+++ b/doc/forum/Problems_with_FAT_links/comment_4_0a5f0239b3b6376672c8d91eaf68a460._comment
@@ -0,0 +1,20 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2016-10-31T18:32:54Z"
+ content="""
+There have been some problems some time ago with the symlink bit getting
+lost on information in the git repository when git-annex makes commits
+on a FAT filesystem.
+
+That was resolved in early 2014, and there's a test case to make sure that
+particular problem doesn't come back, so make sure
+you are not using a git-annex version from before then.
+
+Please check that core.symlinks is set to false. Can check it by running
+`git config core.symlinks` and see if it outputs "false"
+
+I have tried to reproduce on FAT, `git annex drop` followed by `git annex
+sync`, does not seem to do anything to the symlink here. If you can
+reproduce such a thing happening, it's certianly a bug.
+"""]]