tags 487458 + help confirmed
thanks
I agree this would be a nice feature, as cruft's reports can easily get
unreadable because of their size.
However cruft does not have a notion of "tree", it just processes lists
of filenames. Consequently, making it recognize whether a whole subtree
is implicated, would be rather difficult. I'm not saying "impossible",
because both lists of implicated and existing files are available.
However my algorithmic skills are not good enough to attempt writing an
efficient implementation myself. I will happily accept patches, though.
In the meantime, you can have a look at #291823 and its blocker bug, for
a crude UI to cruft reports.
regards,
Marcin