summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://jaen.saul.ee/id/ <Jaen@web>2014-10-30 19:04:57 +0000
committerGravatar admin <admin@branchable.com>2014-10-30 19:04:57 +0000
commite359e0250ecaed4a91827b79cfb71c848172eba7 (patch)
tree62d5afacf3893cf24d54069ac31d3ec62a0afdad
parentd43bf0b05f57bfda7e679d59dd6c0de0cbe0d6fb (diff)
Added a comment: Re: why this happened
-rw-r--r--doc/bugs/annex_get_fails_from_read-only_filesystem/comment_5_07f612d7059a9b561c48d63e471d5ed7._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/annex_get_fails_from_read-only_filesystem/comment_5_07f612d7059a9b561c48d63e471d5ed7._comment b/doc/bugs/annex_get_fails_from_read-only_filesystem/comment_5_07f612d7059a9b561c48d63e471d5ed7._comment
new file mode 100644
index 000000000..24b7dd118
--- /dev/null
+++ b/doc/bugs/annex_get_fails_from_read-only_filesystem/comment_5_07f612d7059a9b561c48d63e471d5ed7._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://jaen.saul.ee/id/"
+ nickname="Jaen"
+ subject="Re: why this happened"
+ date="2014-10-30T19:04:56Z"
+ content="""
+I agree that at least read-only support should be there. This error was from an filesystem type that is impossible to mount read-write.
+
+Now that I am looking at it again with fresh eyes, I suppose it's possible to get around this by mounting an union filesystem with a read-write temp layer on top of the read-only one (not that a regular user would ever figure that out...)
+"""]]