WolverinDEV

I'd thought about the system in the recent time and think, I came up with a pretty need system. Currently I've mainly focused on the `backup` function (my test dummy...

Hey, most of the work has been done. All nutmeg process bars have been factored out into the binary and logging is now done by using `tracing`s logging functions. Additional...

Hey, I've not yet had time to go trough your reviews, but I've merged this PR with the main branch as well (hopefully) fixed the CI failure.

> Overall there's probably more we could do but it's a big step in the right direction. Yes there is a lot more. The monitors also enable a lot of...

> perhaps the monitor interface should look more like something that just accepts `Event` and `Problem` enums. I had the same thought at the beginning, but didn't go for it....

The more I think about it, the satisfied am I with the amount of callback methods currently supplied. I'll think any experiment a bit more as well.

Hey, I've been pretty busy with my last exam for this semester but I had a couple of thoughts about the enum thing. I intuitively used separate functions since I...

@sourcefrog any notes on the changes made?

Hey, just a quick thought: What happens if we mix a backups with different block size in the same archive?

> This might be connected to https://github.com/sourcefrog/conserve/pull/175 just fixed by @WolverinDEV which is one cause of repeatedly re-reading files. What @road2react describes seems to be pretty much, what I experienced...