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 (file)
index 0000000..a4c8c90
--- /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 d4352ccf7ff39075da10dacfe3f836c08cffe646..805a45ca74a9ab4dddf0d35ac3ec80a2200b0b6f 100644 (file)
--- 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]]