Michael Eischer
Michael Eischer
> This isn't hard, but it's kind of tricky to get all the paths right and properly tested. I'd be happier if there were a less complex solution for the...
Yes, the behavior of `restore` is probably also a good guidance. That command for example also continues when some files cannot be written (won't happen for `dump`, but the philosophy...
Related to https://github.com/restic/restic/issues/4804
Please have a look at #3611 .
Related to https://github.com/restic/restic/issues/4478
> I wrote a small POC for this change. If no one is already working on it I would try to follow the PR that implemented this feature on Windows...
A clean solution would be to support `-` as filename when the completion should be printed on stdout. In that case restic should automatically disable the verbose status output. For...
When the destination is not a terminal, then by now the `writing [...] completion file to [...]` is no longer shown by now.
> Would this change also allow to detect windows reparse points which cannot be backed up ? I'm not exactly sure what you mean by that. Starting from Go 1.23.0,...
> I've asked this once before here, is there a way to have a (optin) option to exclude reparse points from backups (like `--no-windows-reparse-points`) ? There is https://github.com/restic/restic/pull/4990 although it's...