work around strange auto-init bug
authorJoey Hess <joeyh@joeyh.name>
Fri, 30 Jul 2021 22:36:03 +0000 (18:36 -0400)
committerJoey Hess <joeyh@joeyh.name>
Fri, 30 Jul 2021 22:36:03 +0000 (18:36 -0400)
commitb3c4579c7907147a496bdf2c73b42238d8b239d6
treef8ba6ad89a2a145068bbe535ea02e0be4cfb66bb
parent9f94d2894e09f47d86d3a2349a458499236041a7
work around strange auto-init bug

git-annex get when run as the first git-annex command in a new repo did not
populate unlocked files. (Reversion in version 8.20210621)

I am not entirely happy with this, because I don't understand how
428c91606b434512d1986622e751c795edf4df44 caused the problem in the first
place, and I don't fully understand how skipping calling scanAnnexedFiles
during autoinit avoids the problem.

Kept the explicit call to scanAnnexedFiles during git-annex init,
so that when reconcileStaged is expensive, it can be made to run then,
rather than at some later point when the information is needed.

Sponsored-by: Brock Spratlen on Patreon
Annex/Init.hs
Annex/WorkTree.hs
Assistant/MakeRepo.hs
CHANGELOG
Command/ConfigList.hs
Command/Init.hs
Command/Reinit.hs
Command/Upgrade.hs
doc/bugs/initial_get_of_unlocked_file_fails_to_populate_pointer.mdwn