From 37cd9864597462170278aebbd8c8adb33e355404 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 11 Oct 2017 12:12:35 -0400 Subject: followup --- ...mment_5_d8c8b725ee91a899a131bf505bd9a2e3._comment | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/bugs/--shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_5_d8c8b725ee91a899a131bf505bd9a2e3._comment (limited to 'doc') diff --git a/doc/bugs/--shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_5_d8c8b725ee91a899a131bf505bd9a2e3._comment b/doc/bugs/--shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_5_d8c8b725ee91a899a131bf505bd9a2e3._comment new file mode 100644 index 000000000..05ef7377a --- /dev/null +++ b/doc/bugs/--shared_setting_of_git_causes_annex__39__ed_files_to_be_writeable__33__/comment_5_d8c8b725ee91a899a131bf505bd9a2e3._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 5""" + date="2017-10-11T15:59:16Z" + content=""" +It's easy to have multiple versions of git-annex installed. Especially +when a repository is shared amoung users, who may install different +versions for their own reasons. + +I am not happy either about this weakening of safety guarantees that indirect +mode repositories otherwise have. It seems at least worth a big fat +warning. + +I don't feel comfortable changing locking without a major repository +version change, which would be a Big Deal. + +Anyhow the file mode and directory mode are both needed to protect annexed +files. Making the file read-only will not prevent a lot of things +renaming over top of it. (Including vim!) +"""]] -- cgit v1.2.3