From 86b64e6acf59dc1759066a769820a114b943b711 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 31 Oct 2016 14:46:40 -0400 Subject: [PATCH] comment --- ..._0a5f0239b3b6376672c8d91eaf68a460._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/forum/Problems_with_FAT_links/comment_4_0a5f0239b3b6376672c8d91eaf68a460._comment 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 0000000000..02cb830d37 --- /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. +"""]]