mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

followup and add link

Browse source
This commit is contained in:
Joey Hess 2020-07-01 12:28:44 -04:00
parent a496ab602d
commit 424b1912d6
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 25 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/design/caching_database.mdwn
View file

@ -1,6 +1,7 @@
* [[metadata]] for views
* [[todo/cache_key_info]]
* [[bugs/indeterminite_preferred_content_state_for_duplicated_file]]
* [[todo/speed_up_git_annex_sync_--content_--all]]
What do all these have in common? They could all be improved by
using some kind of database to locally store the information in an
@ -11,9 +12,6 @@ generated and updated by looking at the git repository.
* Metadata can be updated by looking at the git-annex branch,
either its current state, or the diff between the old and new versions
* Direct mode mappings can be updated by looking at the current branch,
to see which files map to which key. Or the diff between the old
and new versions of the branch.
* Incremental fsck information is not stored in git, but can be
"regenerated" by running fsck again.
(Perhaps doesn't quite fit, but let it slide..)