summaryrefslogtreecommitdiff
path: root/doc/todo/unlock_--json/comment_2_f00fda45d300ce14a5ea6fd32a20defe._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/todo/unlock_--json/comment_2_f00fda45d300ce14a5ea6fd32a20defe._comment')
-rw-r--r--doc/todo/unlock_--json/comment_2_f00fda45d300ce14a5ea6fd32a20defe._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/todo/unlock_--json/comment_2_f00fda45d300ce14a5ea6fd32a20defe._comment b/doc/todo/unlock_--json/comment_2_f00fda45d300ce14a5ea6fd32a20defe._comment
new file mode 100644
index 000000000..294bbcfea
--- /dev/null
+++ b/doc/todo/unlock_--json/comment_2_f00fda45d300ce14a5ea6fd32a20defe._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2017-10-30T18:40:53Z"
+ content="""
+Why was I talking about batch mode here before? --json of course makes
+sense to support for unlock (and lock). Adding that now.
+
+And, to find the files that `git annex unlock` would operate on, you
+can simply use `git annex find`, because that does not list already
+unlocked files, and only files with their content present can be unlocked.
+""]]