From 24378d94e6278ab7f03a1230134a4402bdc21a72 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 28 Jun 2019 15:57:05 +0000 Subject: [PATCH] Added a comment: read-only unlock of only some files --- .../comment_5_645bccbcd3499eb552a24563cb613af2._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/unlock_--read-only/comment_5_645bccbcd3499eb552a24563cb613af2._comment diff --git a/doc/todo/unlock_--read-only/comment_5_645bccbcd3499eb552a24563cb613af2._comment b/doc/todo/unlock_--read-only/comment_5_645bccbcd3499eb552a24563cb613af2._comment new file mode 100644 index 0000000000..06aea71a48 --- /dev/null +++ b/doc/todo/unlock_--read-only/comment_5_645bccbcd3499eb552a24563cb613af2._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="read-only unlock of only some files" + date="2019-06-28T15:57:04Z" + content=""" +There are still use cases for read-only unlock of just some files. One issue with symlinks is that Docker doesn't follow them. So if I want to let Dockerized code read annexed files, I have to unlock them first. But, if these files are to be only used as input, unlocking them for modification is not really what I want to do. I don't want `git status` to list these files as modified. +"""]]