comment

doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_17_c41b669837be95b731bd68f1b3269fef._comment

@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 17"""
+ date="2021-06-04T17:37:30Z"
+ content="""
+The scan could be done lazily, but there are situations that use the
+database where unexpectedly taking a much longer time than usual
+would be a real problem. For example "git add".
+
+The bloom filter idea does not work.
+"""]]

doc/todo/speed_up_keys_db_update_with_git_streaming/comment_3_f4a816ecc43528913f6a97bf1c50dd38._comment

@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2021-06-04T17:45:21Z"
+ content="""
+It is not very useful to detect if a key is used by more than one file if
+you don't know the files. In any case, yes, the keys db is used for a large
+number of things, when it comes to unlocked files.
+
+[[todo/numcopies_check_other_files_using_same_key]] has some thoughts on
+--all, but I doubt it will make sense to change --all.
+"""]]

doc/todo/speed_up_keys_db_update_with_git_streaming/comment_4_2d39ba9ea61fd8006d1fd4fdde8fc055._comment

@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2021-06-04T17:49:43Z"
+ content="""
+Keys with extensions do not necessarily have the same extension as used in
+the worktree files that include/exclude match on.
+
+I'm not sure why all these wild ideas are being thrown out there when this
+todo is about a specific, simple improvement that will speed up the git
+part of the scanning by about 3x? It's like you somehow consider this an
+emergency where increasingly wild measures have to be taken to prevent me
+from making a terrible mistake?
+"""]]