Restore include and exclude are mutually exclusive

[764287]

@fd0

When mixing the patterns it gets messy fast:

$ restic backup \
   --exclude '*.go' \
   --exclude ~/work/secret \
   --include ~/work/secret/project \
   ~/work

Should restic archive ~/work/secret/project/foo.go ? What takes precedence?

That’s indeed a difficult topic. I’d assume some want it as simple as possible and others want it to be as powerful as possible. I could imagine 2 approaches.

1. Allow mixing include and exclude and set precedence by reversing the order they are entered. While this is obviously quite powerful it can become very complicated aswell.
2. include always takes precedence over exlude. This approach isn’t as powerful as the first approach but is easy to understand (and debug).