From 752a7e765fc6ea449c892ddf0564cddb6ac2e439 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 31 Oct 2016 14:14:42 -0400 Subject: [PATCH] comment --- ...t_1_4cd41dca533de8147027eeb9a8ad89db._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/todo/unlock_--json/comment_1_4cd41dca533de8147027eeb9a8ad89db._comment diff --git a/doc/todo/unlock_--json/comment_1_4cd41dca533de8147027eeb9a8ad89db._comment b/doc/todo/unlock_--json/comment_1_4cd41dca533de8147027eeb9a8ad89db._comment new file mode 100644 index 0000000000..5a7136a23d --- /dev/null +++ b/doc/todo/unlock_--json/comment_1_4cd41dca533de8147027eeb9a8ad89db._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-10-31T18:04:04Z" + content=""" +`git annex unlock` only operates on files that are symlinks and link to +.git/annex/objects. +I don't think that `find` provides a way to check the link target +of a symlink, so you'd have to write a program to do it. I suppose +that `git annex find --locked` could be made to do that. + +`git annex unlock` often has to make a copy of the content of a file, +which would be the majority of its IO. Only if you're using +`annex.thin` with v6 might it not need to copy the file, and then a batch +mode could speed it up. Are you? +"""]]