From 9d181ef87f5b4cabda3d66193494b2dfe76fbefc Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 19 Feb 2016 14:47:08 -0400 Subject: comment --- .../comment_5_c6c8850aefe3ab81f1f113daa734695b._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/todo/make_annex_info_more_efficient/comment_5_c6c8850aefe3ab81f1f113daa734695b._comment diff --git a/doc/todo/make_annex_info_more_efficient/comment_5_c6c8850aefe3ab81f1f113daa734695b._comment b/doc/todo/make_annex_info_more_efficient/comment_5_c6c8850aefe3ab81f1f113daa734695b._comment new file mode 100644 index 000000000..3e1cacc80 --- /dev/null +++ b/doc/todo/make_annex_info_more_efficient/comment_5_c6c8850aefe3ab81f1f113daa734695b._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 5""" + date="2016-02-19T15:58:17Z" + content=""" +When run on a local repository, git-annex info does not look at the +git-annex branch. That would be slower than traversing the directories. +(Asking for info about a remote does look at the git-annex branch.) + +git ls-tree does not have to look at files on disk, so is not comprable. +The work `git annex info` does is roughly the same as a du of +.git/annex/objects and a readlink of each symlink in the work tree. + +If you just want the .git/annex/objects size, perhaps it would make sense +to have a way to get only one stat from git-annex status. Or perhaps +it would be as good to `du .git/annex/objects`? +"""]] -- cgit v1.2.3