Allow carving only

[dorpvom]

• Added command line option
• Applied early exit before extraction (@martonilles)

[dorpvom]

Regarding depth:

Yes, using this obviously enforces depth = 1. I would add a logger.debug for this as it is trivial when understanding the option. It would also be possible to make it a warning if depth is not the default, and one can assume it was changed on purpose.
I would probably put that into the cli method in unblob/cli.py, but I'm happy for suggestions.

[vlaci]

Thanks for sending this PR!
I see that you already had some discussion with the guys in #486 about this feature. I am sure they'll look at it as soon as they are able.

[qkaiser]

@dorpvom could you clean up your commit history and provide a single commit ? I see changes within the same code blocks in processing.py from both a875789 and f5a9490. Also d658210 should not be there.

We recommend using semantic commit messages, yours could be feat: add carve-only capability with corresponding command line switch (-s). Do not hesitate to provide a detailed explanation of what you did within the commit message body, this is how we document things.

[dorpvom]

@dorpvom could you clean up your commit history and provide a single commit ? I see changes within the same code blocks in processing.py from both a875789 and f5a9490. Also d658210 should not be there.

We recommend using semantic commit messages, yours could be feat: add carve-only capability with corresponding command line switch (-s). Do not hesitate to provide a detailed explanation of what you did within the commit message body, this is how we document things.

@qkaiser So I'm not usually in bed with rebasing and force-pushing but I guess I got this history where you want it. Any additional requests?