projects / git-annex.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 63a3ced) | patch
finalize RepoSize database
authorJoey Hess <joeyh@joeyh.name>
Thu, 15 Aug 2024 15:50:01 +0000 (11:50 -0400)
committerJoey Hess <joeyh@joeyh.name>
Thu, 15 Aug 2024 16:29:34 +0000 (12:29 -0400)
commiteac4e9391b4a8bb363e87c2bfb2acc89f3de17d0
tree2a47b34d94611cb05b9f1a2a2fac4bb393aca6f9tree | snapshot
parent63a3cedc457ef005f6b1f78b30021996acf0edd2commit | diff
finalize RepoSize database

Including locking on creation, handling of permissions errors, and
setting repo sizes.

I'm confident that locking is not needed while using this database.
Since writes happen in a single transaction. When there are two writers
that are recording sizes based on different git-annex branch commits,
one will overwrite what the other one recorded. Which is fine, it's only
necessary that the database stays consistent with the content of a
git-annex branch commit.
Annex/Locations.hs diff | blob | history
Database/RepoSize.hs diff | blob | history
doc/todo/git-annex_proxies.mdwn diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.