Closed hhyyrylainen closed 1 month ago
It is a file like any other. Why should it be treated differently?
You have the option to a) exclude it (as you said), b) place it somewhere outside of your deduplication directory tree if you want to, e.g., save the deduplication time.
Just my two cents.
I just noticed that after deduplicating other stuff duperemove is now deduplicating parts of the hash file:
This is using duperemove 0.13. Is this intended behaviour? This seems a bit like a bug to me as I need to manually specify an
--exclude
to skip processing the hashfile.