From a255340b1fdb0a7cafd259c1fce46044cfed9b2c Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Tue, 5 Dec 2017 18:20:41 +0000 Subject: Added a comment --- .../comment_6_d0d8065b78c22e62ef780c27e4d5952c._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/--shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_6_d0d8065b78c22e62ef780c27e4d5952c._comment diff --git a/doc/bugs/--shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_6_d0d8065b78c22e62ef780c27e4d5952c._comment b/doc/bugs/--shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_6_d0d8065b78c22e62ef780c27e4d5952c._comment new file mode 100644 index 000000000..b2958d0c0 --- /dev/null +++ b/doc/bugs/--shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_6_d0d8065b78c22e62ef780c27e4d5952c._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 6" + date="2017-12-05T18:20:41Z" + content=""" +> Making the file read-only will not prevent a lot of things renaming over top of it. (Including vim!) + +not exactly... removing write permission from the key file at least makes vim report that the file read-only and disallowing (without force) to overwrite it. That is my use case where I keep burning myself constantly (e.g. this morning again). Need to not forget to switch all \"shared\" repos back to the single user mode. One of the promises of git-annex is that data is safe, and this mode just violates it wildly. +"""]] -- cgit v1.2.3