From acbf711e218f729316ed865ec90d4f5cb59ddcd1 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 16 Jul 2021 15:16:56 -0400 Subject: [PATCH] comment --- ...mment_8_82c04709fe3b69d6a75e44d71b500681._comment | 12 ++++++++++++ doc/todo/cache_key_info.mdwn | 5 +++++ 2 files changed, 17 insertions(+) create mode 100644 doc/todo/Hardlink_keys_with_same_hash_but_differrent_ext/comment_8_82c04709fe3b69d6a75e44d71b500681._comment diff --git a/doc/todo/Hardlink_keys_with_same_hash_but_differrent_ext/comment_8_82c04709fe3b69d6a75e44d71b500681._comment b/doc/todo/Hardlink_keys_with_same_hash_but_differrent_ext/comment_8_82c04709fe3b69d6a75e44d71b500681._comment new file mode 100644 index 0000000000..a4c8c90da7 --- /dev/null +++ b/doc/todo/Hardlink_keys_with_same_hash_but_differrent_ext/comment_8_82c04709fe3b69d6a75e44d71b500681._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 8""" + date="2021-07-16T19:13:36Z" + content=""" +Right. It is possible to get this into a sqlite database and update it +incrementally. The keys database is populated this way, but that's by +tracking changes to the HEAD branch. This would instead involve +tracking changes to the git-annex branch. + +See [[cache_key_info]] for discussion of this kind of thing. +"""]] diff --git a/doc/todo/cache_key_info.mdwn b/doc/todo/cache_key_info.mdwn index d4352ccf7f..805a45ca74 100644 --- a/doc/todo/cache_key_info.mdwn +++ b/doc/todo/cache_key_info.mdwn @@ -35,3 +35,8 @@ data if nothing references it. Or maybe it could be required to have a clean tree with nothing staged before running git-annex unused. Anyway, this is a semi-longterm item for me. --[[Joey]] + +> Update: It seems like #2 has been accomplished now, the keys database +> tracks associated files in all cases now. Although with the caveat +> that there can be stale information sometimes, so it might still not be +> useful for these purposes. --[[Joey]]