From e843334a4099978cfb0314eccf32470c4aca853e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 30 Nov 2020 13:13:56 -0400 Subject: [PATCH] comment --- ...1_006e3e3ab0c08852239c0f8fec851201._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/todo/Make_git_annex_sync_--content_trust_location_logs/comment_1_006e3e3ab0c08852239c0f8fec851201._comment diff --git a/doc/todo/Make_git_annex_sync_--content_trust_location_logs/comment_1_006e3e3ab0c08852239c0f8fec851201._comment b/doc/todo/Make_git_annex_sync_--content_trust_location_logs/comment_1_006e3e3ab0c08852239c0f8fec851201._comment new file mode 100644 index 0000000000..7be5bcc728 --- /dev/null +++ b/doc/todo/Make_git_annex_sync_--content_trust_location_logs/comment_1_006e3e3ab0c08852239c0f8fec851201._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2020-11-30T17:09:28Z" + content=""" +Statting a file is typically much faster than +piping a request through to git, git reading complex files, and git-annex +parsing the result. + +There may be a case, when annex.thin is set, where it has to hash the whole +file to determine if it's got the expected content. Normally this is +avoided by inode cache information though. And if it did, it would only +be slow once for that particular version of the file as it would cache its +informaton. + +If you have a case where this is actually slow, please explain how I can +see it. +"""]]