aawsome

> #3009 won't be able to let `--json` imply `--quiet` as that would break the `backup` command output (the format must not force a certain log level). So this has...

> IMO this works and doesn't break anything Ok, it breaks `find` which uses the `Print` and `Printf` functions to manually generate JSON output :weary: I'll add some more checks...

I thought there would be some changes appearing in near future on either `rewrite` or `prune`, so I waited with an answer. So, basically the point is that restic is...

> With "handle certain types of repository damages" I had in mind that it should be possible to let the prune command tolerate (= be able to remove unused blobs/packs)...

Hi @pddp thanks for reporting the issue! > FAIL github.com/restic/restic/internal/options 0.014s Actually, this PR doesn't change anything on `/internal/options`. Did you redo your test with master? Seems to me that...

I also rebased to current master and resolved all typos in `cmd_repair.go` - thanks @huyz! I'll keep the `troubleshooting.rst` unchanged, is is mainly a topic of #2878 (I think this...

Note that this would be also solved by making prune incremental, see #3806 or https://github.com/rustic-rs/rustic_core/issues/13

@tleydxdy: No one forces you to use `--exclude-caches` - if you want to exclude a priori known (cache) directories, exclude them using `--exclude` or `--exclude-file` - if you want to...

About the comments from #2012: >Few notes/observations > > I suggest to make verify-before-restore behaviour optional. For example, it is likely to slow down restore if the target file system...

@nickchomey You might be right. This PR in fact only restores changed files, but in #2662 the requirements seem to be "only restore changed files" + "remove files if not...