This commit is contained in:
Franky 2020-06-17 19:01:44 +00:00 committed by admin
parent e98f9f7684
commit d72d76c06f

View file

@ -8,7 +8,7 @@ Running fsck on a remote completely drops the file
* Run `git-annex fsck`
* git-annex will notice the corruption and completely drop the file from the remote
I expect git-annex to never drop data unless specified as also mentioned in https://git-annex.branchable.com/walkthrough/fsck__58___when_things_go_wrong/
I expect git-annex to never drop data unless specified as also mentioned [here](https://git-annex.branchable.com/walkthrough/fsck__58___when_things_go_wrong)
I would rather look at the corrupted file myself and figure out the best course of action instead of losing it completely.