Michel Machado

Hi @brianpow, Before we go through code review, could you describe the use case that this pull request intends to help? It doesn't need to be formal or long, I'm...

Having `f3read --delete` does add meaning to `f3write --keep`. I'm going to work with you to review the code and merge it. Let's start making this pull request coherent. First,...

I'm going to leave this pull request open, so someone else can pick it up if the need for it comes. Good luck on your new project!

Hi @efa, `f3brew` writes and reads directly to a block device. I haven't documented it because the only use I've found for it is to help to figure out what...

Using `f3brew` on the entire drive instead of a single partition would destroy the partition table. While I see your point that testing block devices directly is a more complete...

Your point is valid, @silicontrip. But it's so rare that I haven't come across this false negative. I'm not holding back `f3brew`; it's included in the repository here on GitHub....

After all blocks are written, `f3brew` resets the device before reading all blocks back to check. The default reset method requires the user to pull the device of the USB...

You are welcome, @makefu. After your test, post the result here. It'd be informative for many out there.

A pull request to add documentation is welcome.

Your interpretation of the code is correct: `f3probe` assumes that sector wrapping in fake drives is a power of 2. An explanation of the algorithm would be nice to have,...