From d3270a8b9aa7b30125105463546887163115f660 Mon Sep 17 00:00:00 2001 From: "ct.git-annex@230092d9bd3cf09ced2b9605cdb14ad0a3db265d" Date: Sun, 26 Apr 2020 20:18:48 +0000 Subject: [PATCH] Added a comment --- ...0_c2a1f402a28c44f842d88747fa3741cc._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/todo/unlock_--read-only/comment_10_c2a1f402a28c44f842d88747fa3741cc._comment diff --git a/doc/todo/unlock_--read-only/comment_10_c2a1f402a28c44f842d88747fa3741cc._comment b/doc/todo/unlock_--read-only/comment_10_c2a1f402a28c44f842d88747fa3741cc._comment new file mode 100644 index 0000000000..cc5f96276d --- /dev/null +++ b/doc/todo/unlock_--read-only/comment_10_c2a1f402a28c44f842d88747fa3741cc._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="ct.git-annex@230092d9bd3cf09ced2b9605cdb14ad0a3db265d" + nickname="ct.git-annex" + avatar="http://cdn.libravatar.org/avatar/271d3b6a528ac0320c7ac9f296ea9b31" + subject="comment 10" + date="2020-04-26T20:18:48Z" + content=""" +joeyh, could you please elaborate what v7/v8 does different to v5 when unlocking? I don't get it. + +I need this feature (checked out real/hardlinked files while being immutable) as well. Even if it is only a thin layer of protection it may help. Where supported, git annex may use the file immutable attributes (as discussed in https://git-annex.branchable.com/internals/lockdown/) for better protection. + +Imo it's lock/unlock which isn't clear about naming/semantics. We have to things here: 1. symlink vs. direct files 2. protection against mutation. These 2 things mingle together in the current implementation they are different concepts. We can not choose any free combination of these (writable symlink into the object store makes no sense). But a little finer control would be appreciated. No idea how to do this in a concrete way. + +Maybe some 'git annex protect' command to set different protection modes on content (which could be abstract, no need to comply to unix semantics. for example: appendable, writable, immutable, deletable etc. git-annex could enforce the mode lazily if not supported directly) + +or 'git annex rolock' (needs better name) .. which is like unlock but makes the file immutable/write protected somehow. + +"""]] -- 2.39.5