From e0b4fafbb6dfc36c523b86a5d9c9737908557efe Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 26 Nov 2013 19:47:28 +0000 Subject: [PATCH] Added a comment --- ...comment_1_d31018e8bf31d729ee9fee43a0a07934._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/Git_annex_add_fails_on_read-only_files/comment_1_d31018e8bf31d729ee9fee43a0a07934._comment diff --git a/doc/bugs/Git_annex_add_fails_on_read-only_files/comment_1_d31018e8bf31d729ee9fee43a0a07934._comment b/doc/bugs/Git_annex_add_fails_on_read-only_files/comment_1_d31018e8bf31d729ee9fee43a0a07934._comment new file mode 100644 index 0000000000..0a4e61bc57 --- /dev/null +++ b/doc/bugs/Git_annex_add_fails_on_read-only_files/comment_1_d31018e8bf31d729ee9fee43a0a07934._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.64" + subject="comment 1" + date="2013-11-26T19:47:28Z" + content=""" +I cannot reproduce this problem on Linux, with version 4.20131106. I tried in both direct and indirect mode, on Linux. + +I was, however, able to exactly reproduce the error message if I made the *directory* be not writable, and used indirect mode. This is because git-annex has to move the file the .git/annex/objects, and put a symlink in place, and so has to be allowed to write to the directory. Interestingly, direct mode does not have this limiation, although I doubt git-annex would ever be very useful when run in a directory you lack write permission to. +"""]]