Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fdupes improvement #160

Closed
saintger opened this issue Oct 23, 2016 · 1 comment
Closed

fdupes improvement #160

saintger opened this issue Oct 23, 2016 · 1 comment

Comments

@saintger
Copy link

Running the same command twice:

fdupes -r /foo | duperemove --fdupes

Gives exactly the same output result.

It would be nice if files which have been already deduplicated, can be ignored by duperemove (or not included in the output).

@markfasheh
Copy link
Owner

The only way we could remember which files were scanned is if we used a hashfile in fdupes mode. Functionally that's the same as issue #145 so I'm going to mark this as a duplicate. Feel free to watch that bug for updates. I'll update it with your use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants