Kai Krakow

It probably makes sense to stick some stacktraces into the debug level, those which are intentionally created. But those which occur unexpected (the "real" stacktraces) should still be visible as...

Or maybe prevent the exception catcher from generating any output if the original thread intentionally threw and the log level filter does not match DEBUG. Maybe this could be guarded...

@daiaji If the file was created with "btrfs nocow attribute" (see `lsattr`), it won't be touched by bees. That has nothing to do with qemu using a cow format internally...

> On SSDs the seeks are replaced with IO transaction overheads, which are almost as expensive as physical head movements on SATA SSD devices. Wait, what? This sounds much worse...

> Another digression, dedupe can reduce the write amplification of ssd? The block being dedupe has never been actually written to ssd? That's not how bees works: Bees is always...

@daiaji It's still not how bees works: Duplicate data is still written, bees will read it later and find it could be shared. There's no magic algorithm which would say...

@daiaji BTW: If highly redundant data is your primary use-case, you may have better results with content-addressed storage solutions: Git does this, borgbackup does this, ipfs does this, but their...

I've updated the branch. My C++ is a bit rusty these days, mostly only doing Ruby on Rails now. I used to do some Qt programs in the past, with...

The parsing itself would be two-pass. First pass just scans through the config files, identifies the current section, tokenizes the configuration option and inserts or replaces the value in a...

Thinking about your `path =` suggestion: Should be easy to implement it that way, too. I could simply reuse that internally as the section name. I'll make up my mind...