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

comment

Browse source
This commit is contained in:
Joey Hess 2023-08-16 13:16:49 -04:00
parent 4c7e2b167e
commit 5126f6d002
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

22
doc/todo/expose_fsck_last_run_information/comment_1_44f5eb2e601ba1a6cb22f5de7a6d3ff6._comment Normal file
View file

@ -0,0 +1,22 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2023-08-16T17:01:21Z"
content="""
The activity log was built for something else (git-annex expire) and there
would be several problems with repurposing it for this:
* A fsck activity is logged when the fsck starts, if the fsck is
interrupted part way through, or is an incremental fsck, or is a fsck
of only a few specific files, it is still logged.
* The activity log is designed to also support other activities, and only
the most recent activity is recorded. While currently it only has a fsck
activity, it's possible that additional activities be added to support
git-annex expire. That would prevent displaying a fsck after such an
activity was recorded.
It seems like your use case would need a log to be updated only once a
complete fsck was done. Since fsck supports ad-hoc running on specific
files, incremental fscks, fscking of other branches, etc, it's kind of hard
to tell when that has happened.
"""]]