From 5767b9073b8cff628410ef486d648b4acd9e69af Mon Sep 17 00:00:00 2001 From: michalrus Date: Wed, 16 Aug 2017 12:58:25 +0000 Subject: Added a comment --- .../comment_3_78dfedd93393709d3d7e417b779109d4._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/Unlocked_directory__63___Having_all_its_new_files_unlocked/comment_3_78dfedd93393709d3d7e417b779109d4._comment diff --git a/doc/forum/Unlocked_directory__63___Having_all_its_new_files_unlocked/comment_3_78dfedd93393709d3d7e417b779109d4._comment b/doc/forum/Unlocked_directory__63___Having_all_its_new_files_unlocked/comment_3_78dfedd93393709d3d7e417b779109d4._comment new file mode 100644 index 000000000..22a5974c3 --- /dev/null +++ b/doc/forum/Unlocked_directory__63___Having_all_its_new_files_unlocked/comment_3_78dfedd93393709d3d7e417b779109d4._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="michalrus" + avatar="http://cdn.libravatar.org/avatar/83c0b6e7f9d20f09a892263c4903bbae" + subject="comment 3" + date="2017-08-16T12:58:24Z" + content=""" +But it’s better. As a dirty workaround, I could add a cron job/timer that would periodically git-annex-lock all files *except* that single directory I want unlocked. + +But a static configuration—say, in .gitattributes—would be way better. ♥ + +Or is there a way to configure that already? +"""]] -- cgit v1.2.3