From a02b5c2904deff6e762c4caca3fe8b6be468ff67 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 14 Jun 2021 12:36:42 -0400 Subject: [PATCH] response --- ...ent_29_0f3c8949ae362b43ac7db02eb4e11890._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/bugs/significant_performance_regression_impacting_datal/comment_29_0f3c8949ae362b43ac7db02eb4e11890._comment diff --git a/doc/bugs/significant_performance_regression_impacting_datal/comment_29_0f3c8949ae362b43ac7db02eb4e11890._comment b/doc/bugs/significant_performance_regression_impacting_datal/comment_29_0f3c8949ae362b43ac7db02eb4e11890._comment new file mode 100644 index 0000000000..3ab4eb9e6e --- /dev/null +++ b/doc/bugs/significant_performance_regression_impacting_datal/comment_29_0f3c8949ae362b43ac7db02eb4e11890._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 29""" + date="2021-06-14T16:32:38Z" + content=""" +@yarik no, it needs to check all files. Consider what happens when `foo` is +an annexed link to key K, which is not present, and you copy +`.git/annex/objects/../K` from some other repo and run `git annex add K` +(or reinject, or get, it's all the same) -- `foo` now points to the content +of K. The same needs to also hold true for unlocked files, and so it has to +check if `foo` is an unlocked pointer to K and populate the file with the +content. Repeat for all the other 9999 files.. +"""]]