Daniel Pouzzner

yes John just pointed this out to me -- I was expecting the allocator to return an error code, not an `ecc_key *`.

@SparkiDev I've just done some testing on this. First thing I had to change the `armv7a` to `armv7a*` in configure.ac L2050, to accommodate the standard target tuple `armv7a-unknown-linux-gnueabihf`. That done,...

just tried this rebased on latest master, with the configure.ac tweak to recognize `armv7a-unknown-linux-gnueabihf`: ```[cross-armv7a-all-armasm] [1 of 1] [08b4fd6f2e-dirty] autogen.sh 08b4fd6f2e-dirty... real 0m14.917s user 0m13.195s sys 0m0.859s configure... real 0m8.970s...

@embhorn actually IIRC I wasn't digging into the substance of the logic there, just a superficial refactor for the updated macros. The original comment and pragmas were added a little...

retest this please

Thanks @mediatechnologic for keeping the ball rolling on this. I agree there's several things awry with the color picker, and it's often hard to figure out what it's doing.

@gojimmypi OK keep at it -- and please keep an eye out for problems rooted in passing the same pointer as operand and result to SP functions. last week I...

I've just tried a `tar` pipeline, and the metadata block group is growing correctly. At 951.50MiB, it grew from 1GB to 2GB. (update: finished successfully with these allocations: ``` Data,...

Short update: After the `tar` succeeded, I deleted that tree, and reattempted the `btrfs send`. That actually succeeded, to a degree. The `Metadata` block group contracted when I removed the...

@adam900710: >please keep an eye on the unallocated space. What do you mean? The medium is 43% empty. What mitigating action is the user supposed to take? When the syndrome...