From 7187d454d38c673840034d73b3610be79d5f4963 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Tue, 5 Dec 2017 18:20:41 +0000 Subject: [PATCH 1/2] 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 0000000000..b2958d0c0f --- /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. +"""]] From 6c3fa431d96cb05213add5ea1fb1b604c863a2e1 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Tue, 5 Dec 2017 18:26:43 +0000 Subject: [PATCH 2/2] Added a comment --- ...mment_5_09bb754f4e7e19cd52d68f91368f57fc._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/fsck_does_not_detect__47__fix_some_key_directories_correctly/comment_5_09bb754f4e7e19cd52d68f91368f57fc._comment diff --git a/doc/bugs/fsck_does_not_detect__47__fix_some_key_directories_correctly/comment_5_09bb754f4e7e19cd52d68f91368f57fc._comment b/doc/bugs/fsck_does_not_detect__47__fix_some_key_directories_correctly/comment_5_09bb754f4e7e19cd52d68f91368f57fc._comment new file mode 100644 index 0000000000..8356dc2745 --- /dev/null +++ b/doc/bugs/fsck_does_not_detect__47__fix_some_key_directories_correctly/comment_5_09bb754f4e7e19cd52d68f91368f57fc._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 5" + date="2017-12-05T18:26:43Z" + content=""" +FWIW regarding + +> But, that is an expensive operation, needing to copy a perhaps enormous file. So I don't think it's a reasonable thing for fsck to do. + +I prefer machines to do the job instead of me, even though they need to sweat may be more than I for some of those ;) not sure if needs to be an option or default behavior. But altogether, I am trying to get away from shared mode (ref: http://git-annex.branchable.com/bugs/--shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/) with write permissions set on fiels since it is simply too dangerous if that repository is the single source of correct data/files. +"""]]