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

fsck: Warn when required content is not present in the repository that requires it.

Browse source 
This commit was sponsored by Jack Hill on Patreon.
This commit is contained in:
Joey Hess 2018-02-08 14:08:41 -04:00
parent 10bb8a860b
commit 7f5c6a28a6
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
5 changed files with 47 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

10
doc/forum/offsite_repo/comment_1_1f3ab9a39baa16e3e307b23fd1aabeb8._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-02-08T17:32:00Z"
content="""
What you're looking for is probably the [[required_content]] settings.
However, `git annex fsck` did not perform any checks that required content
was present. Now it does. Enjoy!
"""]]

5
doc/git-annex-required.mdwn
View file

@ -22,7 +22,10 @@ While [[git-annex-wanted]] is just a preference,
[[git-annex-required]] designates content that should really not be
removed. For example a file that is `wanted` can be removed with
`git annex drop`, but if that file is `required`, it would need to be
removed with `git annex drop --force`.
removed with `git annex drop --force`.
Also, `git-annex fsck` will warn about required contents that are not
present.
# NOTES

4
doc/required_content.mdwn
View file

@ -16,3 +16,7 @@ by simply using `git annex drop`. On the other hand, required content
settings are enforced; `git annex drop` will refuse to drop a file if
doing so would violate its required content settings.
(Although even this can be overridden using `--force`).
Also, `git-annex fsck` will warn about required contents that are not
present.