Posted here as I thought it may be more suitable for discussion.
It would be useful for restic to consider the order of includes and excludes (given via parameters) so that one could override the other. For example, I have a “global” exclude file which excludes backing up .msi files. However, there is one backup job I want to include .msi files, but continue obeying the global exclude file. With the current restic behaviour there’s no way for me to “re-include” *.msi and still use the global excludes.
If restic obeyed the order of the --exclude-files and --files-from, I’d be able to use the latter to re-include the *.msi files.
The excludes are always applied after --files-from. Depending on you exclude patterns, it might be possible to use negative excludes, for example !/path/to/keep/