summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/Git-annex_not_properly_detecting_symlink_capability_in_CryFS.mdwn1
-rw-r--r--doc/bugs/Git-annex_not_properly_detecting_symlink_capability_in_CryFS/comment_1_78f6f047578974df0dd73740ab05ee8c._comment17
2 files changed, 18 insertions, 0 deletions
diff --git a/doc/bugs/Git-annex_not_properly_detecting_symlink_capability_in_CryFS.mdwn b/doc/bugs/Git-annex_not_properly_detecting_symlink_capability_in_CryFS.mdwn
index ca0131432..bb6280228 100644
--- a/doc/bugs/Git-annex_not_properly_detecting_symlink_capability_in_CryFS.mdwn
+++ b/doc/bugs/Git-annex_not_properly_detecting_symlink_capability_in_CryFS.mdwn
@@ -60,3 +60,4 @@ git-annex-6.20170519-1.fc26.x86_64
I love git-annex.
+> [[done]] --[[Joey]]
diff --git a/doc/bugs/Git-annex_not_properly_detecting_symlink_capability_in_CryFS/comment_1_78f6f047578974df0dd73740ab05ee8c._comment b/doc/bugs/Git-annex_not_properly_detecting_symlink_capability_in_CryFS/comment_1_78f6f047578974df0dd73740ab05ee8c._comment
new file mode 100644
index 000000000..dae2a9d09
--- /dev/null
+++ b/doc/bugs/Git-annex_not_properly_detecting_symlink_capability_in_CryFS/comment_1_78f6f047578974df0dd73740ab05ee8c._comment
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2017-08-28T17:06:35Z"
+ content="""
+git-annex has detected problems with the filesystem, since symlinks
+work I think it detected that the filesystem allows writing to a
+file even when the file's write bit is not set.
+
+In that situation, a git-annex repository using symlinks will apprear to
+work, but if you have an annexed file "foo" in there, and run "echo hi >
+foo", it will follow the symlink, and overwrite the annexed file, ignoring
+the lack of write bit. This can result in data loss in an unexpected way,
+which is why git-annex avoids using the symlinks in this situation.
+
+I've added an additional message to make more clear what is happening.
+"""]]