From 47f16c891596436657ff6076c94f839e47f00ebf Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 2 Jul 2019 18:36:16 +0000 Subject: [PATCH] Added a comment --- ...ent_7_3ea1a354bb631539df1ac941e76988e1._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/todo/unlock_--read-only/comment_7_3ea1a354bb631539df1ac941e76988e1._comment diff --git a/doc/todo/unlock_--read-only/comment_7_3ea1a354bb631539df1ac941e76988e1._comment b/doc/todo/unlock_--read-only/comment_7_3ea1a354bb631539df1ac941e76988e1._comment new file mode 100644 index 0000000000..276a5bb591 --- /dev/null +++ b/doc/todo/unlock_--read-only/comment_7_3ea1a354bb631539df1ac941e76988e1._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="comment 7" + date="2019-07-02T18:36:15Z" + content=""" +To \"just to get the dataset and files to be processed, and then possibly even wipe it all out\", maybe you could just use the [[directory special remote|special_remotes/directory]]? + +Which common file systems do not support hardlinking? It seems that [Windows does](https://docs.microsoft.com/en-us/windows/desktop/fileio/hard-links-and-junctions). + +To fix the problem that unlocking a file causes `git status` to report it as changed (\"typechange\"), maybe git-annex could [tell git to locally ignore the change](https://dev.to/nishina555/how-to-ignore-files-already-managed-with-git-locally-19oo)? + + +"""]]