aawsome

I think we should have performance measurements before we change this for release.. Is there a big difference between using `"s"` ans `"z"`? If not, I'd prefer using `"s"`..

Thanks for opening the issue @AlphaJack. Can you please be more specific what is your exact problem with having this 256 empty paths? In fact, yes we could omit creating...

> As long as Rustic works correctly without empty folders Actually I think it won't. But you can open issues for the errors you get when removing empty dirs -...

Thanks @F3-L1x for opening this issue! Can you please write how you did run the CLI command? Did you try to use `--as-path ""`?

First, am I right that your original intend is to run `rustic backup ./` and have it saved as a relative path? I think this should not be addressed using...

Correct handling of paths starting with `.` (including the paths `.` or `./`) should be fixed by https://github.com/rustic-rs/rustic_core/pull/213

> You mean, it should be automatically saved as a relative-path, when using `./` as backup source-path? Exactly. This is also the current behavior if you backup a relative path...

@nickchomey We are trying to prepare a patch version 0.8.1 soon and I think we can integrate the fix there.

@nickchomey Thanks for your suggestion. In fact, out of the 60 services, there are many which most likely will never be interesting as backup storage. And for those we actually...

Thanks @intgr for opening this issue and sorry for the late reply! I think this is somewhat related to a general overworking of how to include/exclude. I created a milestone...