(and fix an old comment's formatting)
This commit is contained in:
Joey Hess 2022-07-12 16:47:49 -04:00
parent f9b667a0cf
commit 323c78b191
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 19 additions and 1 deletions

View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2022-07-12T20:34:02Z"
content="""
Notice that it says "scanning for annexed files", not "unlocked files"
anymore.
The reason it's slower is explained by [[!commit 428c91606b]].
And that was necessary to fix the bad, longstanding bug
[[bugs/indeterminite_preferred_content_state_for_duplicated_file]].
It has to scan every annexed file, not only the unlocked ones,
in order to collect the data to not have that bug.
And the scan got optimised as well as possible, I think, at the time,
see the old issue you filed @yoh,
<https://git-annex.branchable.com/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/>
"""]]

View file

@ -16,4 +16,4 @@ it might need to update a pointer file. Eg, when `git annex get` is run.
Avoiding using the keys db when annex.supportunlocked=false in all such
cases in order to avoid the scan would be effectively the same complexity
as continuing to support v5 repos, which I've NAKed before.
""]]
"""]]