summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authoryarikoptic <yarikoptic@web>2017-10-10 17:56:47 +0000
committeradmin <admin@branchable.com>2017-10-10 17:56:47 +0000
commit57d9b76a8730998191e25bdaea2dc9d0465fddbe (patch)
treeeba3f86c7563bccae35e930b94f0771c8755fe01
parentfe11aaf0595bd7f429a8db514f1abd53876ab54b (diff)
Added a comment
-rw-r--r--doc/bugs/--shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_4_c72e6646e39cc487ea52cd17925a548f._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/--shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_4_c72e6646e39cc487ea52cd17925a548f._comment b/doc/bugs/--shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_4_c72e6646e39cc487ea52cd17925a548f._comment
new file mode 100644
index 0000000..8e7b2ec
--- /dev/null
+++ b/doc/bugs/--shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_4_c72e6646e39cc487ea52cd17925a548f._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 4"
+ date="2017-10-10T17:56:47Z"
+ content="""
+our comments crossed in the hyperspace... ;) yeah -- I would have expected a separate lock file to be used for such cases. Now data loss is really a possibility (almost made it happen since opened the file and wrote it without unlocking, good that I caught it and was able to modify back exactly the way it was). Interactions among multiple versions of annex on the same repo is imho a lesser possibility (would require two different versions of annex being available)
+"""]]