aawsome

> First, you have discovered two bugs: > > * the error handling does not work correctly. Rustic should stop if such errors occur instead of continue.. > > *...

Thanks for proposing this issue! I think I partly understood your intention, but I'm not perfectly sure if I did get all details. Can you clarify your request a bit?...

Ok, I think I might have understood what you mean (or at least I can imagine an algorithm which may suit your needs): - use all snapshots within a given...

Marking this as duplicate because I think #43 will solve this.

> Well... I would say they are related; but I was asking for an option when "forgetting" snapshots which automatically take care of merging snapshots which are being forgotten. I...

@hgkamath Thanks for your suggestions and thoughts. I have to admit I don't know the architecture or bacula/bareos, but for rustic I think the key functionality is backing up to...

> * I don't know how such client/server communication will happens, but keep in mind about latency. So it's bad idea to ask server about every blob. They should be...

I would welcome a PR very much!

> @aawsome Any updates ? Some actions failed, can we fix it ? Yes, seems that some Windows tests are failing. I am speculating as there are no logs available...

@akrabu You are right. There is no special treatment for `--dry-run` with respect to locking and the standard is to lock the repo in restic. But you can try out...